[Feature]: More Dataverse API flexibility

[MarkMpn]

Provide an idea you would like to see in the tool?

SQL 4 CDS uses a wide range of Dataverse operations and additional parameters which are not currently exposed by the dataverseAPI

I could translate most of the requests to one of these API calls, but some key ones that appear to be missing are:

• batch operations
• transactions
• custom headers

Batch and transaction operations would be needed for bulk data changes, and should be useful in various other tools as well.

Additional headers would be needed for working with elastic tables, bypassing plugins etc.

Ideally each of the existing dataverseAPI functions would take an additional optional parameter which would define any additional headers to include in the request.

A new executeBatch function or similar could take an array of requests, each containing an HTTP verb, URL, optional headers and body, and return a promise of results including status code, headers and optional body. The function could also take a parameter indicating if the requests should be executed as a batch or in a transaction, or two separate functions could be provided to provide each version.

Relevant log output

[Power-Maverick]

• Batch and Transaction will be added to the PPTB API (need more thinking on whether to expose them as individual methods or create a generic execute method)
• Additional Headers: @MarkMpn can you provide list of additional headers you'll need. We do not want to open this up for all for security reasons; especially impersonation

[MarkMpn]

For full SQL 4 CDS functionality I'd need:

• Prefer
• CallerObjectId or MSCRMCallerID
• MSCRM.BypassCustomPluginExecution
• MSCRM.SessionToken

I can see that I might want to be able to access If-Match or If-None-Match in future versions, and that other tools might have uses for MSCRM.SolutionUniqueName, MSCRM.SuppressDuplicateDetection and Consistency as well, and other variants of MSCRM.BypassCustomPluginExecution such as MSCRM.BypassBusinessLogicExecution, BypassBusinessLogicExecutionStepIds or SuppressCallbackRegistrationExpanderJob

It would also be necessary to have access to the headers of the responses to requests as well as the body, e.g. to handle rate limiting or preserve consistency when working with elastic tables