[CoE Starter Kit - BUG] Admin | Sync Template v3 fails if Environment creator does not have a display name

[Mmace123]

Describe the issue

Admin | Sync Template v3 fails in the Check if Legacy Environment section, when trying to run the Get Maker child flow if the environment does not have a creator listed.

We have one environment where that is the case, and always fails.

Expected Behavior

I would think it should be able to still run regardless of the environment creator being there or not.

What solution are you experiencing the issue with?

Core

What solution version are you using?

3.45

What app or flow are you having the issue with?

Admin | Sync Template v3

Steps To Reproduce

1. Have an environment where no creator is listed.
2. Run the flow.

Anything else?

No response

[Jenefer-Monroe]

I've not seen this before but also don't have many users with legacy environments.

Please make sure you don't have unmanaged layers on this flow Remove unmanaged layers from inventory flows
And that all the helper flows are turned on

If those are ok, please share a screenshot of the point of failure

[Mmace123]

No unmanaged layers.

Error is:

"error": {
"code": "TriggerInputSchemaMismatch",
"message": "The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected String but got Null.'."
}
}

I think it may be less that the creator doesn't exist, but that it doesn't have a name associated with it.

I did a test with the previous version of the flow, and can get it to work by checking if the creator name is null and then sending through System as the creator name instead. But, have not changed this version.

[Jenefer-Monroe]

OK this isn't a legacy environment, its in the other branch, so that makes this a much more commonly hit.
However I've never seen one come through without display name. We can take a look but it wont be able to be in for Oct as I will have to look at the helper function.

[Jenefer-Monroe]

I believe the fix here would be to just place the following equation in the location shown. Can you please apply the fix locally and let us know if it resolves for you?

if(equals(items('Apply_to_each_Environment')?['properties/createdBy/displayName'], null), '', items('Apply_to_each_Environment')?['properties/createdBy/displayName'])

[Mmace123]

Yes. That seems to have fixed the failure. Thank you.

Just ran it, and it went through without issue.

[Jenefer-Monroe]

Thanks for testing for me! Fix will ship with Nov release.