Jenefer-Monroe
commented
1 year ago Hello I'm so sorry you lost your metadata.
Unfortunately a record being missing from a refresh in the only way we know that an object (envt etc) has been deleted. We look for that (for envts) here CoE BYODL - When Environment dataflow refresh is complete:
When we detect these cases we do not delete them though we only mark them deleted.
The delete itself happens in this flow CLEANUP - Admin | Sync Template v3 (Check Deleted) dependent upon an envt variable.
So the way to avoid this happening, so that you can restore these records, is to use that env variable, set it to No, and then while we will still mark these objects deleted, you could fix up the dataflow issue and then they would be restored with their metadata.
We dont have that env var set to no by default to avoid capacity overage. So its recommended if you do this, to have a periodic flow on your own side that will delete these after some time when you feel they are safe to remove (perhaps after 6 months of being marked deleted or something like that)
nwmb
Does this bug already exist in our backlog?
Describe the issue
We upgraded the COE Toolkit with the BYODL, and honestly, its been quite painful because of the lack of clear documentation - predominantly regarding the dataflows.
During the last upgrade, I got the updates installed. Removed and reinstalled the Power BI dataflow via the Power BI workspace (didn't seem there was a method to update using the .json file?) and was feeling pretty proud. I forgot, however, about the dataflows that exist in the COE environment and couldn't find documentation to reference on the upgrade process when BYODL in place.
Fast forward to today, it appears that the connection information in the dataflows within the Power Platform environment was reset during the upgrade and the dataflows have been failing. This is a relatively easy fix and I've been working through getting those updated to run again - however, the more painful piece, is that it appears the failing workflows may have wiped out the environments, apps, flows, etc. tables within the COE.
Unfortunately, the environment records had been assigned descriptions and use cases and other metadata that went away with the deletion of these records. I'm not sure if something else is at play here, but looking for advice and wanting to raise this in case it happens to others!
Also, if there is a good document that outlines how to upgrade the COE with BYODL on - please share!
Expected Behavior
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.16
What app or flow are you having the issue with?
BYODL Dataflows
What method are you using to get inventory and telemetry?
Data Export
Steps To Reproduce
No response
Anything else?
No response
AB#263