on
RE:
100% agree. They can currently email it to themselves and then save to sharepoint so it makes no sense why restrict to Contributor role. As mentioned, options for these users are to build a flow via Power Automate (which most do not have the bandwidth to learn) or engage a ticket with the IT dept to set up a subscription for them.
RE:
Why was this removed? Seems insane to me
RE:
Problem is solved, no need for further analysis. Please remove the above idea. Thank you.
RE:
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.
RE:
I am joining to this idea with my idea of improving Odbc.Query function to trigger only one query instead of two.https://community.fabric.microsoft.com/t5/Power-Query/Odbc-Query-triggering-only-one-query/m-p/4385658
RE:
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!
RE:
Hi Team,I'd like to request an enhancement to the Journey creation flow to allow users to select or change the Form both during creation and after, without needing to delete the Journey. This would reduce confusion and improve the user experience.Thanks!
RE:
It is there, but you have to select the individual series to format. There is currently no way to format it with "all" as the cards may have different data types.
RE:
This would be super helpful, otherwise I need to create two charts to give the necessary granularity choices.
RE:
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.