NavigationMixin default values(muti-select picklist) are not considered in experience cloud

[pavanbhat1999]

Summary

NavigationMixin behaving strangely for only experience builder and only for multi-select picklist Default values are passed to the NavigationMixin. The whole code is working properly in lightning app. But multi select picklist values are not getting populated in experience builder.

Salesforce Org Type

Developer Edition Org

Steps To Reproduce

No response

Current Behavior

Other field are auto populated but Multi Select Picklist not Autopopulated in experience builder

Expected Behavior

Every fields should be auto populated in experience builder

This is working in Lightning App

Relevant Log Output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

Welcome! 👋

Thank you for posting this issue. 🙇🏼‍♂️ We will come back to you latest within the next 48h (working days). Stay tuned!

[adityanaag3]

Hi @pavanbhat1999 I tried to reproduce the error, but I couldn't - I tried in both a dev org and a pre-release org, and default values for multi-select picklists worked for me.

I used the navToNewRecordWithDefaults recipe, so please compare your code to the recipe to see if anything is different, and please let me know.

[pavanbhat1999]

@adityanaag3 Okay I checked it again.

Code works for an independent multi-select picklist. But it does not work for dependent multiselect picklist

[adityanaag3]

Thanks, @pavanbhat1999 - I've reached out to the concerned team internally, and am waiting for a response. Will keep you posted.

[PratapDronadula]

@adityanaag3 @pavanbhat1999

Any Luck. on this

Even In My LWC Js File I need to Prepopulate the controlling picklist Field Value and Dependant picklist Field Values in Record Creation through Navigation Service. But Controlling picklist Field value is populating however dependant picklist value is not populating

[pavanbhat1999]

@adityanaag3 Any update on this. LOL! it is more than a year

[adityanaag3]

@pavanbhat1999 Apologies for the delay. I have escalated this internally and should hear a response soon.