Hello all,
I don't post often, but this one has me stumped. I'm getting an error in the portal for one environment (Test) with objects that work just fine in another (Dev). I've looked at the supporting objects involved and I cannot see a delta (nor could compare and deploy). Event the portal being referenced in Test works fine except for this one area. I would appreciate advice on what other avenues I should be looking at. Below is the error and script from the 2 environments.
Discussion posts and replies are publicly visible
You can check multiple things:Check The portal isn't published in Test or has different permissions.Try a!urlForPortal() Without any parameters. If this works, the issue is with how the portal handles the parameters you're passing.If this doesn't work, then the portal's internal interface likely references something (record type, data store, integration) that's misconfigured in Test.
Anything in the tomcat stdout log file?
You can try Exporting the object and related precedents from dev and import in test manually - without using Compare and Deploy! Check If any inspection errors are there or not. In absence of errors you can deploy and see if it works or reports any errors. Give it a try as Sometimes a Re-deployment can fix or flag the issues not found otherwise.
If it’s working in Dev but failing in Test, it could be an environment-specific configuration issue rather than the objects themselves. I’d check:
Environment variables / constants – sometimes a value like a URL, credential, or feature flag is different in Test.
Security settings – user/group permissions in Test might be missing or different from Dev.
Data source connections – ensure Test is pointing to the correct database or API endpoint.
Version mismatches – confirm the Test environment actually has the latest deployed version of all dependent objects.
If everything matches, try exporting the object from Dev and reimporting into Test to rule out corruption or hidden changes.
Regards:
Team https://talksocially.com/
I'm new to reading these, but I'm seeing something here that may be a clue. The UUID in line one is the object that's quoted in the error shown on the portal. If there is a "missing" object, suggestions on tracking it down? You'd think the missing object's uuid would be mentioned in the log.
2025-08-08 14:15:41,218 [pool-91-thread-1] INFO com.appiancorp.portaldesigner.messaging.AffectedPortalsCalculationKafkaConsumer - Portal a86461c0-27fd-4ada-94bc-7738939fecd6 will be auto-published as a result of a change in object of type Interface with uuid _a-0000eba2-07af-8000-9bfa-011c48011c48_671219 2025-08-08 14:16:22,847 [pool-87-thread-1] ERROR com.appiancorp.type.handlers.RecordType2Handler - Failed to find uuid attribute with namespace [Namespace: prefix "a" is mapped to URI "http://www.appian.com/ae/types/2009"] + in the XML element
Turns out this was tied to product bug ticket LCP-18438. The fix has been released in a new hotfix for 25.2. Once the portal was reset, everything started working again. Thank you all for your inputs.
Thanks for updating us here!