[CoE Starter Kit - BUG] Get_toWhom_profileo issue with the "Assign to all" button in the Request Orphaned Objects Reassigned (Child) flow

[Marius-Bjorni]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

We got the following error message when a user pressed the "assign to all" button in the orphaned objects process:
"WorkflowOperationParametersRuntimeMissingValue. The 'inputs.parameters' of workflow operation 'Get_toWhom_profile' of type 'OpenApiConnection' is not valid. Error details: The resolved string values for the following parameters are invalid, they may not be null or empty: 'id'"

It seems like the issue is that the toWhom is empty:

But according to issue 8362 #8362 this problem should've been fixed?

The flow looks like this:

Using the june 2024 version of CoE.

Expected Behavior

No error message

What solution are you experiencing the issue with?

Governance

What solution version are you using?

3.24

What app or flow are you having the issue with?

Request Orphaned Objects Reassigned (Child)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Hello, thanks for posting. This issue was posted and fixed for the June 2024 release of the kit. Please see #8362

[Marius-Bjorni]

Hello, thanks for posting. This issue was posted and fixed for the June 2024 release of the kit. Please see #8362

That's exactly what I also pointed out.
And I'm on the June 2024 release, which is why I created a new issue. The problem doesn't seem to be fixed, or this is another seemingly similar issue.

[Jenefer-Monroe]

oh sorry I got mixed up by the version number you listed.
When we did the testing for this fix, "No data entered" is what is sent in to Get toWhom profile, which sent 404 status code to the switch statement.
It looks like this product behavior may have changed and due to some competing priorities investigating this will have to go on the backlog.

[Marius-Bjorni]

That's okay :)

Are there any temporary workarounds we should use?
Or should we just inform the affected end user and ask them to do it correctly next time they receive the same email?

[Jenefer-Monroe]

I think for now that's all I can advise for now, to not do that. I would have to debug to see what expression will work now instead. Hopefully I can do that in the next couple weeks.

[Jenefer-Monroe]

I just got around to testing this and it does appear to still work for me. I'm not sure how you are not getting 'No data entered' as I did.

Can you try this equation? I can't test as I dont repro, but I did validate that I still work with this expression instead.
@{coalesce(if(equals(length(coalesce(outputs('Send_Table_For_Response')?['body/data/toWhom'], '')), 0), 'No data entered', outputs('Send_Table_For_Response')?['body/data/toWhom']), 'No data entered')}

Here is what I see

[Jenefer-Monroe]

An early release of the August bits are available for testing.
Please see our Preview Builds

Please test for us! But do not install these in your production environment but rather in a test envt to get us feedback.

Here are the August release candidate solutions.
Core 4.33.14
Gov 3.24.1
Nurture 3.18.1

And the PBIT files
Production CoE Dashboard August 2024
Governance Dashboard August 2024

It contains all the changes targeting August: https://github.com/orgs/microsoft/projects/195/views/59

Including these two very impactful changes:
#8016 - Update Kit to respond to new Power Platform Admin Role PIM feature
#8482 - Integrate new audit log methodology into the kit for API reduction. Please see issue for setup instructions.

[Jenefer-Monroe]

fixed in August release https://github.com/microsoft/coe-starter-kit/releases/tag/CoEStarterKit-August2024