Dear Akanksha, thank you for reaching out, blank/empty/null values can be tricky. In case you haven’t found a solution in the meantime, I hope our findings are helpful for you. If we understood your requirements correctly, that you need to be able to offer an “empty” option in a multi-selection filter, below is what we did to make it work. In order to be able to share the page XML with you, we used only Salesforce standard objects and fields: Opportunity object and the fields “Name” and “NextStep”.

1. Override field metadata of the "NextStep" text field so that it's displayed as a picklist.


2. Manual picklist entry: XYZ


3. Please note that we didn't add an extra "blank" option.


4. Added an inactive condition named "NextStepEmpty" to filter for empty values.


5. Added an inactive condition named "NextStepValue" to filter for multiple values.


6. Condition Grouping Logic: "1 OR 2"


7. Added a filter of type "Multi-select Option" to the Table component.


8. Pick Options and Condition(s) = Manually


9. Model Condition to Affect = NextStepValue
   


10. Now we added two different manual sources, first: Picklist option to affect the default condition.


11. And "Manual" to affect the other condition, simply to "Activate" the "NextStepEmpty" condition.

Please note that we created this V1 test page in the latest Skuid version: 12.2.15
In case this doesn't do what you expect and you use an older version, we recommend to upgrade a Sandbox to test this page (As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes after you upgraded).

If it still doesn’t show the expected result, please share more information about the result you see on the test page and the result you would expect.

Regards, Luzie & team

---