How do I use the "is in" filter in Domo Campaigns Markup Language?
I have read this page on Domo campaigns and distribution lists:
. I see that "is in" is a filter option to include multiple possible values in a filter, but I can't figure out the correct way to write the list of options without having an error in the campaign. I've tried several ways including the following:<dataset id>.column is in OPTION1, OPTION2
<dataset id>.column is in (OPTION1, OPTION2)
<dataset id>.column is in OPTION1; OPTION2
<dataset id>.column is in [OPTION1, OPTION2]
Can someone please show an example of how this filter can be written?
Additionally, the page I linked says "You can also add paginated Mega Tables and Pivot Tables in the email body and PDF attachments. To learn more about Mega Tables, see Table Chart." Does this mean that you can create a table that wont be cut off by the height/width specified in the HTML of the email body? How can I have a table card that includes all content in the filter, even if it is longer than expected?
Thank you!!
Best Answer
-
It shouldn't have a problem with spaces if they are in the correct place. Beware of leading or trailing spaces. Many languages are picky about case sensitivity. Make sure you match the correct spelling and case. And check data types of your filters.
** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0
Answers
-
Similar to other languages would be:
student_courses.course_type is in (English, Science, Math)** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0 -
Is there a restriction on strings with a space? When I have a list like (Option1, Option 2, Option 3), it is only returning rows that match "Option1" with no space. Enclosing the strings in single or double quotes had the same result.
0 -
It shouldn't have a problem with spaces if they are in the correct place. Beware of leading or trailing spaces. Many languages are picky about case sensitivity. Make sure you match the correct spelling and case. And check data types of your filters.
** Was this post helpful? Click Agree or Like below. **
** Did this solve your problem? Accept it as a solution! **0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 101 SQL DataFlows
- 622 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 748 Beast Mode
- 60 App Studio
- 41 Variables
- 688 Automate
- 177 Apps
- 453 APIs & Domo Developer
- 48 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 397 Distribute
- 114 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 126 Manage
- 123 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 109 Community Announcements
- 4.8K Archive