thank you for your reply.
I looked into those things and played around.
The Microsoft Dataverse connector led me to connect the data to powerBi, to check the situation.
Unfortunately, the Approval and Approval Request tables (or any other table about approvals "msdyn_flow_" via dataverse) only show me either the approvals I triggered or sent to someone due testing. I dont see any data about someone else with access to the list started an approval flow for a certain item or how often and with what result, etc...
Additionally I cant wrap my head around this data for each item, e.g.:
There are no names except the "owner" which in my case is myself.
Maybe this needs further processing?
And as i mentioned, i can assure that the tables from the dataverse dont contain any approval flow (the "button" one &or the automate-request signature type) started by someone else with access to the list.
Is that correct?
This means i cant use the microsoft dataverse approach atm.
The workaround i try now is to run a flow where i check the current item version and store the link to that item first.
Then get the version-histories array, get rid of everything except each versionnumber and check if they match the current one. (No side-versions by-the-way, they are deactivated because i cant activate them somehhow, it doesnt let me)
This way i can create a combined approval's & item-version history and store/track this information and most important send whats going on via email.
All done by "if item modified" trigger with condition checkers who check the value of ApprovalStatusValue.
So i get a flow where i can process requesting and answering and attach for each the information about the current item version and the approval history, to know which versions so far got an approval or got rejected.
So far i would call this ok. But the next point makes me worry.
To not just have this information stored elsewhere l need to show it on the list item.
This means i would need to update the item and that makes me worry because i was able to avoid that a flow is updating items.
What makes me worry is that the update-item action creates a new version history. This means it will cause that the just set up flow checked version-number doesnt match with the item shown in the list by at least +1.
The only solution to that selfmade problem is to soft-overwrite the version number in the previous flow.
What i yet don't know is how to include the case of a stopped request.
Well...
It would be handy if one of those approval flows would actually store an item-version in the version-history of the item where the ApprovalStatusValue 0,1,2,3 is being shown in each case.
My entire workaround here or the dataverse part is based on my initial problem.
Maybe i got them wrong, here are my questions:
Only 365 users can right click on an item to execute a power automate flow?
Do i have to share the power automate flow to each person with access to the list, so they can use them?
If not, i need to use the out of the box approval worklfows until the majority got the 365 installed. Which is my current conclusion.
Thank you very much.
Best regards!
