https://community.telligent.com/community/14/Verint Community 14 significantly improves performance, efficiency, visibility, resiliency, and upgrading.en-US14.0.0.684 14https://community.telligent.com/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-ui/1624104Fri, 13 Nov 2026 11:55:00 GMTforumreply:1624104Karl Barber is out today, but this doesn't answer the question. You can clearly see from Karl's original screenshot, that the assembly version is set and shows in File Explorer as 33.1.0.26 but in Community it is shown as 33.0.0.0. We know how to set the assembly version, but Community is only showing the major version, so we cannot see which assembly versions are deployed.https://community.telligent.com/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-ui/1624103Fri, 13 Nov 2026 07:01:00 GMTforumreply:1624103The custom assemblies panel currently displays the .net assembly version, which is often fixed and doesn't change between builds. [quote userid="278531" url="~/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-ui"]Is it possible to alter the information shown ? [/quote] re: your question Yes, for your own custom plugins, you can set the assembly version per build in the csproj file (e.g. 14.0.12.0 ) , and after you rebuild and redeploy, the panel will show the exact build. Please test this first, as changing the assembly version can break binding if other assemblies reference that plugin. For 3rd party libraries, the assembly version is fixed by the vendor, so it can't be changed on your side.https://community.telligent.com/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-ui/1624102Thu, 12 Nov 2026 09:15:00 GMTforumreply:1624102Local instance of 14 build 684, as you can see from the screen grabs the version in the community is only show the major value for some dlls and also not showing any date values as per previous versionshttps://community.telligent.com/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-ui/1624100Thu, 12 Nov 2026 07:15:00 GMTforumreply:1624100Version information listed under the custom assemblies panel should match the version displayed under the file’s Properties > Details. Could you please let us know which site this is?https://community.telligent.com/community/14/f/ask-the-community/1152662/how-are-custom-assembly-versions-determined-for-the-admin-uiTue, 10 Nov 2026 17:49:00 GMTforum:1152662Looking in the new custom assemblies panel the version number does not fully reflect the details from the underlying dll so it is not possible to confirm which exact version has been deployed, esp on a saas environment for example CsvHelper shows as 33.0.0.0 but has more specific details in the dll This is also the case if we look at some of our own custom dlls such as the ticketing app which simply shows as 14.0.0.0 rather than the specific build Is it possible to alter the information shown ?https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624045Wed, 14 Oct 2026 14:28:00 GMTforumreply:1624045Yes the compose file from How do I get started with installation? has the version (644) which appeared to work for Justin McCullagh after updating the search ver from 619 to 639 but not for me I also have a separate build from the dev example page which has 684 and 639 and that also shows the same error re searchhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624044Wed, 14 Oct 2026 14:09:00 GMTforumreply:1624044It appears to are still running 644 and it should be 684 of communityhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624042Wed, 14 Oct 2026 08:44:00 GMTforumreply:1624042Hi Patrick M. I started it again this morning As per Justin's comments I had changed the baseline compose file and updated, but it still shows the warning in the web monitoring as before Before I tear it down and try again another clean setup is there anything else we can checkhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624041Tue, 13 Oct 2026 15:45:00 GMTforumreply:1624041The restart may have been the key, until the restart its possible that the community still thought the search was wrong. It would take some checking but that would explain why it seems code wise t be fine.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624040Tue, 13 Oct 2026 15:40:00 GMTforumreply:1624040Yes, it cleared after restart but I also removed the 619 image before my restart so it was just 639 that remained, not sure if that made a difference.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624039Tue, 13 Oct 2026 15:35:00 GMTforumreply:1624039To clarify, if you restart the containers does the issue on the schema go away?https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624038Tue, 13 Oct 2026 15:04:00 GMTforumreply:1624038Yep, same schema status issue. Same for another dev here too. The initial yaml just has 619 in the setup docs, on clean setup its showing the issue from first start but updating to 639 and restart does fix ithttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624037Tue, 13 Oct 2026 14:31:00 GMTforumreply:1624037Do you get the schema status issue as well? So far in my review if you are running 639 then you should also not have that issue so its a bit perplexing unless its not truly updatedhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624036Tue, 13 Oct 2026 13:00:00 GMTforumreply:1624036I had the same issue using the yaml in the setup docs How do I get started with installation? I had to update search to 14.0.0.639 manually to resolved the issuehttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624034Thu, 08 Oct 2026 21:55:00 GMTforumreply:1624034ok I will have to look at the other error, I had hoped you were just having a version mismatch but will look deeperhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624033Thu, 08 Oct 2026 16:15:00 GMTforumreply:1624033Also tried a new clean 'dev' env install and this works but also still had the search error, which doesn't seem to stop search working in either set of builds D:\Dev\Community.14.Test\HelloCommunity\.devcontainer>docker compose pull [+] pull 38/38 ✔ Image af1.verintconnect.com/dfe-community/community/search:14.0.0.639 Pulled ✔ Image mcr.microsoft.com/mssql/server:2022-CU20-ubuntu-22.04 Pulled ✔ Image alpine:3.24.1 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/infra:14.0.0.644 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/web:14.0.0.684 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/job:14.0.0.684 Pulled ✔ Image af1.verintconnect.com/dfe-community/community/installer:14.0.0.684 Pulled ✔ Image mcr.microsoft.com/dotnet/aspire-dashboard:13.6.0 Pulled ✔ Image axllent/mailpit:v1.27 Pulledhttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624032Thu, 08 Oct 2026 15:49:00 GMTforumreply:1624032There were 2 issues I can now pull down af1.verintconnect.com/dfe-community/community/search:14.0.0.639 so that should fix the issue with the plugin template asking for 639 which then didn't exist, thanks for that In my clean test env How do I get started with installation? I've updated search in there as a test from 619 to 639 F:\Docker\Community V14 Test\community>docker compose pull [+] pull 23/23 ✔ Image af1.verintconnect.com/dfe-community/community/installer:14.0.0.644 ✔ Image axllent/mailpit:v1.27 ✔ Image af1.verintconnect.com/dfe-community/community/infra:14.0.0.644 ✔ Image af1.verintconnect.com/dfe-community/community/search:14.0.0.639 ✔ Image mcr.microsoft.com/dotnet/aspire-dashboard:13.6.0 ✔ Image mcr.microsoft.com/mssql/server:2022-CU20-ubuntu-22.04 ✔ Image alpine:3.24.1 ✔ Image af1.verintconnect.com/dfe-community/community/job:14.0.0.644 ✔ Image af1.verintconnect.com/dfe-community/community/web:14.0.0.644 This still shows the search error,but not sure if this was what you meanthttps://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624031Thu, 08 Oct 2026 15:18:00 GMTforumreply:1624031Can you retry 14.0.0.639 and let me know if it works now?https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624025Thu, 08 Oct 2026 13:55:00 GMTforumreply:1624025Thanks Patrick M.https://community.telligent.com/community/14/f/ask-the-community/1152642/clean-install-has-errors-re-search---content-search-schema-is-incorrect/1624024Thu, 08 Oct 2026 13:54:00 GMTforumreply:1624024The community.telligent.com error I will look into, but it can be safely ignored, its a service that is just looking for product updates. I will look into the search issue. If this is development and you don't specifically need search you should be fine but it will still show the error. The newer image is an updated SOLR but not functionally different.