on
RE:
Dear Amit,thanks for posting that idea. We need exactly the same functionality!Best Regard
RE:
Agree. The web source can not be set up in the Gateway either so then when published the author of the report has to OAuth on it which means it's no longer running on an established service account and the ramifications of that from attrition are terrible. IT will follow policy to only use gateway based connections but citizen developers use what's available to them and many times that is a file in a Sharepoint folder. We have set up on-prem file folder connections in the Gateway for groups that do a lot of self-service development and have been pushing them to use that instead for this reason, but PBI pushes to use Sharepoint, especially now that Save to OneDrive/Sharepoint is baked into subscriptions.
RE:
IS there any update on this as RLS does not work correctly, this could evne be added to the app so we can hide pages in the one report
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!