コメント
-
It sounds like you want to calculate on-time deliver percent on sales orders (document /order number), not lines. Your beast mode tags each line as on-time, late, or whatever - rather than each order. You probably may need something with a FIXED() CASE WHEN MAX(CASE WHEN `SO OTD Tag` = 'Late' THEN 1 ELSE 0 END) OVER…
-
If you want to use variables, you could create variables for comparing date range A with date range B. You will need a start and end for A range, and a start and end for B range. Then use a beast most to identify what belongs to range A and what belongs to range B. Filter out the other. CASE WHEN `Date` BETWEEN `Start Date…
-
You can track the calendar differences by using your primary date field and creating fields for year({datefield}, month({datefield}, monthname({datefield}) and the use aggregates in Magic ETL to calculate current year, previous year, previous 2 years, etc. How deep you decide you need is based on whether you need it down…
-
One way would be to use a beast mod calculation to create a column as a "reclass". CASE WHEN `Location` LIKE '%LOVES%' THEN 'LOVES' WHEN `Location` LIKE '%TA%' THEN 'TA' WHEN `Location` LIKE '%SPEEDWAY%' THEN 'SPEEDWAY' ELSE 'OTHER' END Opps…I accidently entered before I was done. That would create a new row for each:…
-
Have you tried using the Rest API with append? POST https://api.domo.com/v1/datasets/{datasetId}/data?updateMethod=APPEND You mentioned looking for reference page. https://developer.domo.com/docs/tools/domo-js
-
You are using: domo.post(/data/v1/${datasetId}, [submission]) but I don't see where you are running this as a brick or app. Have you deployed this as a app within Domo? We can't see the whole manifest in your screenshot. Do you have it set to write? Otherwise, it might be treated as read-only. "dataSets": [ { "name":…
-
This isn't my area of expertise but maybe we can get some discussion going to help you solve it. Yes, I would think concatenating fields would help with the uniqueness and avoid your upsert issue. It would simplify the logic of what constitutes a unique record. Maybe create a new field with something like:…
-
If the objective is a column with the current date or date/time, why not just use a function tile?
-
When you say it was successful - do you mean it says it was successful, or that you actually got your data back from the executed code? The error suggests the user is not authorized to access that dataset. The domo.ds_get() fetches meta data or schema but probably fails on the retrieval of actual data. Token or account may…
-
I don't like having those icons up there, at all. I'd rather see Domo spend time coding a default for variables (100+ upvotes) then adding icons we don't need. When we started using Domo I was told we could request removal of "Buzz" from the interface. I did request it be remove but it is still. Maybe you get to request…
-
I don't have the available time to work through an example. This is just how I would approach the problem. I would try setting up the webform and set permissions where owner is the logged-in user. Make sure it filters PDP to that specific person only. So feedback editing is allowed only for them. If Domo won't allow it to…
-
If you click on that gear, does it show the App name with a form to change it?
-
Ha ha ha. Email them - support@domo.com.
-
If it's a repeatable issue, I think you should log it with Domo Support. Since it works in Domo AI Playground but not workflows, there seems to be a limitation in workflow's image to text. They probably use a different API. Or there may be something in the image metadata that's an issue.
-
How about a webform with a dataset that holds your task data: time, type, follow-up, owner, and feedback. Display the data in a table and use filters and PDP (personalized permissions) to restrict users to only their tasks? And have them edit the webform to update their feedback? Or you could create a custom brick using…
-
That looks like a Domo error that isn't your fault. Appears to be a Java exception error with a trace error code. Domo Support can possibly track that ID back to what caused the error. Could be just a glitch in the Matrix. Do you continually get that error? What kind of image? JPEG, PNG? How big was the image? Check your…
-
1. Before the loop, create an empty List of Objects variable (invoiceLogList). 2. Inside the loop, add to List of Objects • Define keys: invoiceNumber, isSent • Add each invoice's log info to invoiceLogList. 3. After the loop ends, use the Append to Dataset tile. • Set invoiceLogList as the input. Now you're writing all…
-
Reference to a similar question: https://community-forums.domo.com/main/discussion/66762/getting-buzz-message-when-a-form-submitted
-
You are splitting the string by comma. Replacing value equals with actual values. This may work in the preview because the data is consistent. But in execution you will have inconsistent field structures like extra spaces, missing fields, extra commas, new line variations, etc. You might try trimming whitespaces after…
-
I don't think you can use html on a normal text card. You can use a Notebook card, brick, app, or image card.
-
The problem appears to be with the character set interpretation. The CSV UTF-8 is a universal standard for encoding text. Especially special characters such as non-English. If Excel saves using default csv, it is limited in the characters it supports and may truncate or skip sections. But 17% data loss sounds extreme. I…
-
You can use Domo’s Magic ETL to simulate recursion if your hierarchy isn't too deep or large. Filter rows where ManagerID IS NULL (top-level). Join the result to the hierarchy where ManagerID = EmployeeID. Repeat the above as multiple steps (one per level).Append each level's result together. You’ll be limited by the…
-
I'm going to venture a guess and say you expecting too much from the SQL tile. When it was introduced to us, we were told it would have limits. Having the SQL tile reference itself isn't something I'd expect it to do.
-
A bit difficult to visualize without an anonymized data example. I'm thinking there's an issue with NULL.
-
What about using FIXED? Something like SUM(`served`) FIXED (BY `Physical County`, `CABINET`) / NULLIF(SUM(`passed`) FIXED (BY `Physical County`, `CABINET`), 0) * 100
-
Your code looks like its sending JSON as a string rather than sending as JSON. This might work once, but then fail if it can't be properly parsed as JSON. This const appDBQuery = `{ "content.ac_page_id": { "$eq": ${pageID} } }`; appears to create a string. Try it as const appDBQuery = { "content.ac_page_id": { "$eq":…
-
Have you tried using a generic Domo JSON Connector?
-
Can you just put Physical County and Cabinet on a card and then add a formula (beast mode) as (SUM(`served`) / SUM(`passed`)) * 100 Your group by is in essence the Physical County, Cabinet.
-
I believe the total row at the bottom will give the same aggregation as you have above. You could create two versions of the column, a second one for sum. Pivot tables would give more flexibility for creating custom aggregations.
-
This link may be helpful: