An issue is observed with Coupa connector where a boolean attribute ‘invoicing-user’ value is neither visible at Application’s Accounts tab nor it is extracted using api. On screen, the ‘invoicing-user’ is not visible at all and from api, the value extracted is “null”.
We confirmed that ‘invoicing-user’ value is available at Coupa tenant and verified from api call using Postman/Bruno. When Coupa connector was initially configured, we extended the schema for ‘invoicing-user’ attribute along with two more similar boolean attributes and these two are visible from UI as well as returnable from api call.
From debug page, user’s attribute looks like following, as if it is string type:
<entry key=“invoicing-user”/>
Other two similar boolean attributes are looking in following format, which is expected: <entry key=“invoicing-user”> <value> <Boolean> </value> </entry>
Please advise if someone has faced similar issue in past.
Hi and Hello, @smahajan
welcome in the SailPoint Developer Community
The issue you’re encountering with the Coupa connector, where the boolean attribute invoicing-user is not visible in the application’s Accounts tab and is being extracted as null via the API, seems to stem from a misconfiguration in the schema definition.
Specifically, the invoicing-user attribute is being treated as a string instead of a boolean, which is evident from the format shown in the debug page
(<entry key=“invoicing-user”/>).
Go back to the schema configuration of the Coupa connector and specifically check how the invoicing-user attribute was defined.
Ensure that the invoicing-user attribute is correctly defined as a boolean. Its entry should look like the other boolean attributes.
Even if the schema is correct, sometimes caching issues in the interface or API can cause attributes not to be displayed or updated correctly. Try clearing any caches related to the connector or application.
Permissions: Check if the invoicing-user attribute has the correct read/write permissions. If this attribute is restricted, it might not be visible in the application’s interface or returned by the API.
As a last resort, you can try removing the invoicing-user attribute from the connector schema and re-adding it to force proper synchronization of this field. This step may help fix any internal mapping inconsistencies.
Hi @AdamVentum , we tried to clear the cache couple of times. Permissions are also looking well as we are able to retrieve the value from Postman/Bruno using the same credentials.
We tried couple of steps to troubleshoot this. Removed the attribute from schema and ran the account aggregation and refresh identity cube but it didn’t help.
We also deleted the complete application from iiq console, created application one more time with sync jobs but issue still persists.
From debug page we picked a Coupa link/account xml and replaced attribute’s string tags with boolean tags forcefully. Though it temporarily solves the issue as attribute values starts showing up, but if sync jobs are run again, it goes back and replaced with string type.
Let me see if anything can be captured and shared here from trace logs.
