- UNIFYBroker Forum
- UNIFYBroker/Aurion
-
Questions
Aurion PersonNumber is a required field and is not present
I'm not sure that this is really a product issue but raising a ticket in case this has been encountered before. I've connected to a cloud instance of Aurion. The agent Test Connection returns correctly but when I try to import on the Person or Employee connectors, I get a schema validation warning with a warning in the error log "The entity <null> (GUID) in the connector Aurion Employee failed validation 1 times for the following reasons: EmployeeNumber is a required and is not present". Same thing on the person connector but I get it for PersonNumber. The query has been scoped to one user for testing. When we run the report in the Aurion App we can see the PersonNumber in the XML. I tried turning on the trace logging in the exe config but it's not outputting any files, is this because the connection is https? It seems the report is running but either has no data at all or the key field just isn't populated. Any ideas?
Answer
The account running the query has been given super user rights with the same result.
Hi Dan,
Broker requires that the key field is unique and populated in the connector. In this instance, it sounds like something is happening with the report which is meaning it's not returning all populated fields. Ensure that the report Aurion is spitting out doesn't contain any null users or extra records
Thanks Adam, it was the schema mapping. I thought the UNIFYAssure template would have the correct values since we provided the report as well but they're different for whatever reason. The PersonNumber schema attribute was mapped to Person_Number for example. It needed to be PersonNumber. Thanks for the direction. The mapping is there because the query to Aurion contains different field names to what is returned, is that right?
The sample has the mapping set.
For future reference, the mapping is required because the default schema field names (which are mapped to the export API fields) don't necessarily match the import field names.
Customer support service by UserEcho
The sample has the mapping set.
For future reference, the mapping is required because the default schema field names (which are mapped to the export API fields) don't necessarily match the import field names.