Server side permissions for embed programmatic filtering not working with private embed
I am able to access my dashboard with the embed links set to private using server-side permissions. However, when I log into an account that have filters set, I get the following error:
{"status":400,"statusReason":"Internal Server Error","path":"/embed/pages/5yv8Z","toe":"6EH2UGS74M-ES1C9-R929I"}
I am fairly new to all of this and trying to figure out why the filtering would be blocking access.
Answers
-
Are the pfilters getting set correctly and have you validated the format of passing in the pfilters? Have they been url encoded?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
Thanks Grant for responding. The pfilters work when the embed is set to “public” but I am not sure how to go about validating how the pfilters get passed. I have a feeling that is the problem. I likely have not “url encoded". So I how at least have something to hang on to in searching for a solution. Here is a sample of how I have a filter set up:
filters: [{"column": "Source / Medium", "operator": "IN", "values": ["luminary / partner"]}]0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 602 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 692 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 386 Distribute
- 111 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 113 Manage
- 110 Governance & Security
- 8 Domo University
- 30 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive