Open Cathi029 opened 1 year ago
It appears we don't have a Cleanup helper for those. At this point we are blocked from investing in these until the modern dataverse connector supports x-envt.
Putting on the feature backlog and marking as blocked as a result.
@Jenefer-Monroe, @manuelap-msft could we mark RPAs as deleted using similar logic as we have in connection identities flow comparing current in CoE vs actual returned from the Process table?
We could but we are hesitant to spend the time on this given how broken desktop flows are today anyway due to the legacy connectors limitations. The plan is to have Desktop Flows be the first thing we fix up with the new connector as soon as its ready so we can shore up this feature end to end. If you have some reasons that this woudl make sense to spend now anyway, please reach out to us! We're happy to get your feedback.
@Jenefer-Monroe Thanks for the info! If the support of environment selection in new DV connector will be out soon then definitely no sense to start changing flows using legacy connector. Hoping that it will be available GA this month like stated in the roadmap 🙂
Describe the issue
Hi all,
Flows for synchronisation do not notice if a desktop FLow has been deleted. I created one, in Power Automate Desktop App. The Flow has been added to the Dektop flow table. When deleting the Flow, this is not reflected in the Kit. After a few days (and sync runs) the deleted Flow is still visible in the Kit.
Expected Behavior
Deleted Flow not showing up after one day.
What solution are you experiencing the issue with?
Core
What solution version are you using?
3.53
What app or flow are you having the issue with?
Sync Flows / Admin View App
Steps To Reproduce
Anything else?
No response
AB#1100