Unanet Refresh Issues BTech BTech Alerts & Notifications - Check this page for the latest information on emergencies and system outages. All times are Pacific. Category: Integrations Category: Integrations - Non BTech Product ManagersIntegrations Overview, 1000060230. Integration Information We frequently observe some integration-related problems with refreshes in Unanet. A few scenarios that were noticed are listed below. Password Update in Boomi: The production password may get copied over to the sandbox during data refreshes, changing the existing sandbox password for integrations.This will result in '401:Unauthorized' exception while invoking the Unanet APIs. In this case, verify if the password configured for Unanet Sandbox is different from Unanet Production.If the password is different, try testing the APIs by modifying the password in Postman. If it works, update the password in Integration configs. API Key Licenses in Unanet: We've noticed that occasionally, API key licensing might not be carried over with a Sandbox refresh. Although the keys might be there, they might not be authorized. This will cause an exception of '401:Unauthorized' when attempting to use the Unanet APIs. Check with Unanet support to confirm the license status of the API keys.As soon as the necessary licenses are obtained, APIs should immediately start functioning seamlessly. Integrations Web Server password reset in Unanet: Unanet triggers the Boomi web service whenever there's an update to an opportunity. The integration username and password are stored in the Unanet workflow. If the Pjob isn’t showing up in CMiC and no errors are present on the exception dashboard, it’s possible that Unanet's calls aren't reaching Boomi. Please check the integration credentials and ensure the configurations are correct.
