[CoE Starter Kit - BUG] Wrong default environment ID in Dateverse Cloud and Apps tables

[maikletal]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.
  Same error that [CoE Starter Kit - BUG] Wrong Environment ID for Default Environment Sync #5595 in new version

Describe the issue

Between Friday the 9th and Monday the 12th of June we have updated the CoE to the latest version and we have detected that since then the new power automate flows and new power apps that are detected in the Default environment are being saved with the identifier without the word "Default-" before it.

This issue is causing that new and deleted flows or apps not be detected correctly and the Power Bi dashboard is also not working well.
We don't know what causes this error because the default environment is still accessed with the word “Default-“ in front of it.

We need to resolve this error.

Expected Behavior

We expect the correct ID with "Default-" word in Environment ID when save the data in dataverse tables.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.9

What app or flow are you having the issue with?

unknown

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

1. In CoE environment
2. Got to Flows dataverse table
3. Filter by dafault environment ID
4. Verify that the field "Flow Environment ID" have different values for the same deafult environemnt.

Anything else?

[maikletal]

Is it possible to delete the content of the "Power App Apps" and "Flows" tables in the CoE so that the information of the flows and applications of the default environment is regenerated?

[Jenefer-Monroe]

If you arent storing any metadata about these objects then you could do that yes.

Or if you are storing metadata, then in 4.9, there is a flag on these objects requesting they be re-inventoried. This can be flagged manually in the Power Platform Admin View app

Or you could write a quick flow to mark this field for all flows / apps in default as true (Yes). Then the next time your inventory runs they will be re-inventoried.

[Jenefer-Monroe]

That issue there of the text field showing id instead of name, I will look into

[maikletal]

I attach the data of the version that I have installed

Now, I'm using the new Audit Logs inside Core Components and I stopped Audit Logs Solution.

What is the correct data? The one that has "Default-" or the one that doesn't.

[Jenefer-Monroe]

Yes it appears this column has actually stored the envt name not the envt id as string in the past.
So I have updated the flows to do that again.

Change is in these two spots

[maikletal]

Hi Jenefer.
Ok. So, to fix the problem I have to edit those two flows so that the data is saved correctly. That will create an unmanaged layer that I will have to remove in the next COE update, where I assume the bug will be fixed.
To correct the data in dataverse, I can create a flow that gets the wrong data and update the envId field or correct the two flows first and use the re-inventory option, right?

[maikletal]

Hello again Jenefer,
I am reviewing both streams and they already save the "envtid" value (image attached). Is the correct value "envtname" or "envtid"?

[Jenefer-Monroe]

envtname is correct.
envtid and envtname are the same value except for things like default evnt which prepend a string. Thats how we got this bug when we replatted to v4.
Thank you for posting!

[CoEStarterKitBot]

@maikletal This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.