Issue with accessing a Power Virtual Agent Property using Composer

[tamasschilp]

Describe the bug

I want to set a Power Virtual Agent property in Composer. I use the "set a property" composer function to set the PVA property "powervirtualagent.buergerbueroContact"

The mentioned property is used in a specific PVA flow initially.

The PVA throws the error "Cannot convert variable new_variable"

A problem occurred while running the Composer dialog. Cannot convert variable new_variable_f0ed4e95838e44bfa65eb28d87f2238e_eb6e3060e7d94d9a9f964566d67cd344 to a namedEntity

Do I do anything wrong?

Thank you

Version

2.0.0

Browser

• [X] Edge

OS

• [X] Windows 10

To Reproduce

see bug description above

Expected behavior

The property value is set in Composer, so I can skip several questions in the PVA topic flow to output a specific information.

[iMicknl]

@tamasschmolcz the PVA screenshot below, is that your 'Burgerburo' flow? Could it be that you are using this property within Composer, before it is created in Power Virtual Agents?

If that is the case, I am not sure if this is a supported scenario. https://docs.microsoft.com/en-us/power-virtual-agents/advanced-bot-framework-composer#use-and-update-power-virtual-agents-variables-in-bot-framework-composer Someone from the team can hopefully respond on the supported scenarios.

[tamasschilp]

@iMicknl Yes I think that could be the root cause for the issue. That would be a pitty, if the flow needs to executed before.

Do you know, if I also can access Composer properties via PVA flow?

[tonyanziano]

There appears to be a bug on the PVA side, and I have filed an issue with them.

I will follow up on this thread with any updates.

[benbrown]

@tonyanziano any news on this?

[tonyanziano]

I just pinged the PVA team and they are still investigating.

[tracyboehrer]

@tonyanziano any news on this?

[tonyanziano]

@tamasschmolcz It turns out that this is currently an unsupported scenario in PVA and is by design, because when using a mutli-choice prompt in PVA it actually stores the value as a ClosedListType variable in the back-end. In Composer, when you are trying to set the property, you are using a string, which is a type mismatch and that is what causes the error.

It might eventually be supported in the future, but for now it is by design.

(Reference: Link to PVA work item)