Wizard steps saying components are out of scope

I'm trying to create some "Enable if" conditions in a wizard to go from one page to the next on a multi-page app. The conditions I'm using are based on a component having an invalid value as false, but I'm getting an error message that the component is not scoped to the app.

Unable to access 'indirectBuyerEmailInput' since it is scoped to 'newConnectionRequest'. 'undefined' is scoped to the app.

Screenshot below.

I tried using a transformer instead, but I'm getting the same error.

Seems like a bug, since the component is on the current step of the wizard itself, so all scoping should be on the same page. Any advice or workarounds to be had here? If this doesn't work, are wizards useable at all with multi-page apps when using the "enable with" conditions?

Hello,

I noticed the same as @eman31:

Where my listview is within the Wizard. However, even though I get the error, the validation still works.

1 Like

Hey @eman31 thanks for reporting this! We have noted this bug internally.

As for workaround in the meantime, I think what @MiguelOrtiz is saying is correct: while you still might get the validation error in the code editor, the logic itself should still work. Are you seeing it still work on your end despite validation error? Or is it broken in behavior as well?

2 Likes

Thanks @Darya_Verzhbinsky , I tested after seeing @MiguelOrtiz 's comment and confirmed it does indeed work. Appreciate both of y'all!

3 Likes

Looks like a fixed has been made for this. Thanks @Darya_Verzhbinsky! This should be rolled out in one of the next few releases. :heart_hands:

2 Likes

That's correct @AbbeyHernandez ! Should be out by end of week.

2 Likes