Has anyone encountered a "Disjunctions not supported" while automating with a flow getting values from a custom metadata? Do you have any recommendations?

From the reading that I did, "Disjunctions not supported" is thrown when an OR condition is used on the SOQL looking up the metadata. [1,2]

In my case, the flow does not have an OR condition on the GET (the SOQL equivalent so to speak). However, I see a pattern that looks like a bulk trigger of the flow throws this error.

Do we know whether a bulk update on the flow generate an OR condition when looking for the metadata in a flow? Is there a workaround that anyone knows about?

Thank you for any help.


  1. Disjunctions not supported

  2. https://help.salesforce.com/articleView?id=custommetadatatypes_limitations.htm&type=0 (SOQL section)

  • 1
    Flow does an OR if the same criteria are used in two places in get records, see this page where it says "When you define multiple filters, the filter logic usually defaults to AND. However, if multiple filters have the same field selected and use the equals operator, the filters are combined with OR."
    – gorav
    Commented Nov 5, 2019 at 23:31
  • Hi @gorav Thank you for the response. Yes, I did see that. In this particular case the filter conditions are all unique. From my research it seems as if when the flow is triggered on bulk records, the GET is bulkified. I am wondering whether that would cause an OR condition. Which would be a Salesforce bug then (?)
    – PAbr
    Commented Nov 7, 2019 at 0:05

3 Answers 3


Salesforce has indicated this is a known issue with no resolution date. https://success.salesforce.com/issues_view?id=a1p3A000001RXPC

The workaround for my situation was to use apex


I also encountered similar issue so replaced my Custom metadata with custom object not ideal. But the reported issue has few affected users so not likely to be fixed anytime soon.

  • This does not answer the question, you will be able to comment on posts when you will have sufficient reputation. Commented Dec 31, 2019 at 7:54
  • @debra anderson - that is an option. Though I would love the ease of deploying the metadata values and also the implied query limits on using custom metadata.
    – PAbr
    Commented Jan 24, 2020 at 2:31

I created a generic lookup service to get around this. Code is here and how-to is here.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .