Comments
You can add the text qualifier to all entity fields without having to browse them all by doing the following :Select all of the lines in the mapping details formClick on the three points in the right of the grid (from where we're used to insert new columns)Click on "Edit selected rows"Select the field "Text qualifier" and "Yes" as a value Click on the "Apply" buttonSave your changesI hope this will be helpful for those who are still facing this problem.
Hi Team,I suggest refining the Journey creation flow by adjusting the order of the steps, so that "Choose the Type of Audience" follows the form selection. Additionally, enabling users to update or select a form after the Journey is created, without having to delete it, would greatly improve usability and reduce confusion.Thanks!
Dataverse has a limit on the number of requests and will return a 429 Too Many Requests error if too many requests within a period of time as per documented by Microsoft: Service protection API limits (Microsoft Dataverse) - Power Apps | Microsoft LearnCurrently, we found out that there are no configurations available to users/administrators for limiting the frequency of API calls done to Dataverse as this is set-up at their service level.
We are aware that there are service limits for Dataverse API based on this documentation:Our understanding is that these limits are there to restrict if there are too many API requests hitting the Data verse service. Can we check if these limits are configurable in any way, or are there any similar settings we could make use of to limit API calls to Data verse in our environment?