GrantSmith Coach

This sounds like a bug. I'd recommend logging a ticket with Domo Support about the issue.

@Nick12 How is your JSON API endpoint telling you about the pages? Have you configured your connector to use that same type of pagination method?

@user049141 This sounds like a bug with the policy auto creation. I'd recommend submitting a ticket with support.

@HalD Is your filtered data returning a single record or are the campaign name, description, start date and status all the same value after filtering? If that's the case taking the MAX of those values will give you the same single value allowing you to display it correctly on your page.

Seems like dynamic page filtering isn't available with the waterfall chart currently then. I'm not certain if this is intended or a bug but you could try and reach out to Domo Support to get a definitive answer.

You can utilize a notebook card on a page and insert dynamic text directly into the notebook using a several summary numbers. When editing the notebook card you can click on the [#] button in the toolbar to insert a summary number. Since it is a summary number you'll likely need to use a min or max on your string fields…

When you click on the waterfall card to filter on your page is there a blue box with a left facing arrow that appears on your waterfall chart? Are there any page filters being applied atop the page?

Does the email address field you're using to join the tables together have the same values in both fields? Can you look at one where the additional data is missing in your master dataset based on the email in the report dataset and see if you can find the same email in the master dataset?

Sounds like a bug. I'd open a ticket with Domo Support if it's doing an Append even though it's set to Replace.

1) Are you using the same column name from the waterfall as other charts on your page? 2) Do you have any card interaction limitations on the waterfall to not apply the filter to the rest of the page?

Do you have some sample anonymized data you could post so I can get a better understanding of your data structure? Any perhaps what you want your output dataset to look like?

Seems like an issue with your CRM system itself in that it can't read information. Are you able to pull the data normally through the CRM UI and is this only an issue when attempting to pull the data via the API / JSON No Code connector?

I was hoping it mirrored the pydomo package but doesn't appear to be the case. What you could do is configure an ETL to do a recursive append every time your rdomo dataset is updated in Domo. Creating a Recursive/Snapshot DataFlow in the New Magic ETL

This is because of using a LEFT join on your dataset. What you're saying is give me all the records in my report table and then give me related information int the master list table if it exists. If you want to get all the data from your master list and supplement it with your report list then you'd need to use a RIGHT…

This is currently how Domo functions. You'd need to share all the pages with the admins (or dynamic group of admins) so they have access to all of the pages.

Have you tried passing in 'APPEND' as the update method parameter in your ds_update function?

In typical Windows fashion - have you tried restarting your workbench server?

You would utilize a Domo Web Form and update your data there and then use an ETL to join it to your original dataset but currently you can't do it within cards.

You'd bring in the dataset that's already in Domo, compare to the records you wish to update and filter out the ones you don't want. You'd only be importing the updated partitions into Domo and Domo would have the existing dataset already on hand The only way Domo can handle removed records is to do a full replace or a…

Have you looked into using a recursive dataflow to "partition" your data and filter out any old records and replace them with new records? https://domohelp.domo.com/hc/en-us/articles/360057087393-Creating-a-Recursive-Snapshot-DataFlow-in-the-New-Magic-ETL If you're using workbench have you looked into partitions?…

Hi @ozarkram What errors are you receiving? Have you use back ticks (`) in your beast mode? Case when `Plant` ='Celes' and dayofweek(`orderdate`) in (2,3,4,5) then '50' when `Plant` ='menes' and dayofweek(`orderdate`) in (2,3,4,5) then '90' end

Hi @shielmunroe, Reach measures how many unique people saw your content. This is calculated on Facebook's end. Whatever granularity you pass to Facebook (Month, Day etc) is what it uses to calculate the uniqueness. So if I happen to view your content twice in a month on two separate days I'd have 2 records of 1 for each…

Hi @thwartted You can't aggregate an aggregate in a normal beast mode. You'd need to utilize an ETL to aggregate your data with a count by whatever grouping you wish and then use that dataset to calculate the average in the beast mode in your card (or alternatively just calculate the average after your count aggregation in…

Hi @RSViju How is your data structured? The filter cards on your dashboard should apply both filters to your dataset.

Hi @ozarkram I'd recommend configuring a date dimension dataset to easier track YOY differences / comparisons. I've done a write up on this topic in the past which you can find here: https://dojo.domo.com/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest You can then utilize a beast mode to…

In workbench you define the upsert key in the job configuration. Are you wanting to enable upsert on a dataset which has duplicate upsert keys already? Each new job would need to have the upsert key defined as each dataset would have different keys.

Create a beast mode and just add your values together: `Field 1` + `Field 2` + `Field 3`

No as Domo would see them as two completely separate servers.

Ah, embeds are unique to the user who created it within Domo so you'd have two separate embed codes since you're using two separate accounts. Not sure why Domo did it that way but that's the current behavior.

Depending on how technical you are you could utilize a Python script and the pydomo package to upload your CSV data straight to Domo. If you have a computer in which you have Workbench installed but don't want to install it on your other computer you could utilize a shared drive which the server with Workbench could read…