For example, for an ID field in a table, you can use Lookup to retrieve the corresponding Name field from a dataset. We need to use Lookup to retrieve the values from the specified dataset for a name/value pair where there is a 1-to-1 relationship.

and if necessary, investigate in our internal logging. To display the parameter label field in the RDLC report we can use the Built-In Lookup function. Would you like to take over the setting?”Īlso, in the future when you post a request/response, please paste the entire raw data (you can remove the authentication token…) so we can see the request Id etc. Also, if you then get into the Portal UI (with the original credentials you use now) and go to the Schedule Refresh page of the dataset, you will see who the owner is now (once you are not the owner, a line appears there saying “the dataset has been configured by ……. You can try (via API, with the same authentication you do) to Take Over the dataset ( ) after that, you should be able to execute Update parameters. You probably are within the same tenant/group (as you can see the data), but not allowed to modify datasets in the way the owner can.ĭo other “Write” APIs work for you? For example Update Datasources (see )? I think you will get the same error. My guess is that you are NOT the same user when you use the APIs, as when you login to the portal.