I have an entitlement endpoint that returns the list of entitlementIDs for a particular user. The http parameters for the endpoint is: /SecurityUserRoles?$count=true&$filter=UserId eq '<<acccount name>>'In the ImportAccountEntJSON -> accEntParams -> ...
For a D365 F&O integration, we've noticed that when using acctEntParams with processingType as "http", the account matching is case sensitive.In the response from the SecurityUserRoles endpoint, the response entries has different case UserIds.For exa...
Looking at Rest Connector's Developers Handbook, in example 3 of the AddAccessJSON section, the example shows two entitlement types: {
"call": [
{
"name": "Group",
...
},
{
"name": "Role",
...
}
]
} If I need to make m...
In our environment we receive account operation requests (Add/Update/Remove Account etc) from an external ticketing system via the SaviyntAPI createRequest endpoint.For Remove Account requests,When a username (XXXXX) and account name (YYYYY) is speci...
Busy reviewing some Dashboards and came a cross a note in the "Understanding Dashboards" documentation: "When you run the DashboardRefreshJob, the chart property is replaced accordingly based on dashboard type."Is it required to schedule the "Dashboa...
@andresvds Looks like the schema file entitlement upload process ignores an "entitlementid" column.We've recently run into a situation where we on-boarded an application via schema file uploads. Subsequently we've switched to a Rest connector, which ...
@skIf I put anything other than a accounts db table column name such as "accountID" for example:"acctKeyField": "#CONST#${String accID = accountID; String ret = accID.substring(0,2).toUpperCase() + accID.substring(2,accID.length()).toLowerCase(); ret...
@sk Your understanding is correct. Account correlation is based on the PartyNumber attribute that links the Worker and SystemUser entities.I've tried with the keyfield, but that does not work.I've tried using colsToPropsMap:"acctEntParams": {
"entTyp...
