Hello @Valentin, The URL pattern is {serverURL}/{metaSourceIDorAlias}/{appIDorAlias}/{table name}. So for example, if we assume the following: The server URL is https://localhost/indicium We want to use IAM as the metasource The application alias is my_appl The table ID is my_table This would give you the following URL: https://localhost/indicium/iam/my_appl/my_table Alternatively, it would be /sf/ to use the SF as the metasource. Other than that, the user that you are authenticating with must have sufficient permissions to access the application and the table in question. To validate whether you can access the application, you can perform a GET request on the following URL: https://localhost/indicium/iam/my_appl I hope this helps Hello, thank you for the response! I have tried using IAM as the metasource before and it still does not work. Peculiarly enough, it does perform a GET call with SF as the metasource (“{serverURL}/sf/...”), but the POST call still gives a 403. This mig
Can you explain what went wrong with the attempt to set this up in a process flow? This should be pretty straight forward to achieve. Hi @Erwin Ekkel,Thank you for the response. Since we were using a grid, the ‘Grid Edit’ action was the only candidate, however it did not fire when starting the flow. We ended up changing our solution.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.