Api fails for filters
Hello folks, need help over domo programmatic filters.
While calling api it's gives us a error https://public.domo.com/embed/pages/my embed ids /stack?parts=metadata,datasources,drillPathURNs,domoapp,slicers,dateInfo&includeV4PageLayouts=false
But i have no idea for what case is happen error logged
`{
"status": 404,
"statusReason": "Not Found",
"toe": "8LHL63C15L-CJSFA-9JTRR"
}`
Any help will be appreciated
Best Answers
-
Alongside this thread and awaiting the advice of the technical adept users, reach out to Support [support.domo.com] to have them look at it as well (and escalate to Dev if need be).
9 -
This is the link: support.domo.com
9
Answers
-
Alongside this thread and awaiting the advice of the technical adept users, reach out to Support [support.domo.com] to have them look at it as well (and escalate to Dev if need be).
9 -
How to contact the domo support they have very late response, and there is no discord channels for support
0 -
You can have your Customer Success Rep help to accelerate the responses once you log the Support ticket.
6 -
Please send the links or way to get the help from domo support. It's urgent i try every possible way
0 -
This is the link: support.domo.com
9 -
Thanks for help and support
1 -
@sunny for your card is the public embed link correct? 404 means it can’t find anything at your URL. Are you able to take that URL and access it from a browser? Did you confirm the embed ID is the same as the Domo Everywhere configuration settings on the card?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
For your card is the public embed link correct? Let me check
404 means it can’t find anything at your URL. Are you able to take that URL and access it from a browser? I try with postman collection here is image for it https://ibb.co/Rv1KbmD
Did you confirm the embed ID is the same as the Domo Everywhere configuration settings on the card? Let me check and get back to you
@GrantSmith Well thanks for help let me check and get back to you
0 -
New error that i am facing. Can anyone help
<h1>Bad Message 431</h1>
<pre>reason: Request Header Fields Too Large</pre>
0 -
Also how did you go with the 404 error? Did Support give reasons to why that was happening and how to resolve it?
6 -
I try with clear cache and also try with postman still same issues
0 -
Hi @sunny, there must be a URL character limit being exceeded somewhere in your request, whether it's through large numbers of fields, or fields with long names, selected. Could you please check the number of fields passed as well as the length of the field names used, and see if any reductions to the size of name or number of fields impacts the issue?
6
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 712 Beast Mode
- 50 App Studio
- 39 Variables
- 668 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 45 Workflows
- 7 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 116 Manage
- 113 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 104 Community Announcements
- 4.8K Archive