Best Of
Re: Single Value Card - Footer use Todays Date mysql like a summary number?
@Canioagain , if you build the date the data was collected into the dataset, maybe you can use a smart text, https://domohelp.domo.com/hc/en-us/articles/4529227357975-Using-Smart-Text
i would strongly urge you to avoid trying to use today() in your card title because IF there was a hiccup in your pipeline and the data hadn't been updated, you'd be misrepresenting the truth. if you build report_date = today() into your ETL, then the timestamp would be as of the last execution time which would always be accurate.
Re: Datasets join issue
thanks for the shoutout @mhouston
Strong agree to the UNION approach instead of JOIN.
@utkarsh it looks like your dataset 2 needs some sort of date column. if each month everyone has the same budget, then duplicate the rows of Input 2 once for each month and add the end_of_month_date column as @GrantSmith describes before UNIONing the data.
Re: If possible, how can I call a Stored Procedure or Function?
@ricsanders and @Jose_Rojas Domo does not really have the concept of stored procedures or functions available for execution in Magic dataflows.
You can create stored procedures in MySql dataflows but i strongly recommend you avoid them because MySQL (v5.6) is significantly more effort to optimize and maintain if you're trying to hand dataflow pipeline design to other users.
for @ricsanders, we typically recommend building your datasets with all the users in it, then just use a Filter Card to select the user you want to display information for in your dasbhoard. -- I can appreciate that xx million might feel like a lot of wasted disk space if you have to read the entire table, but typically for Domo, millions of rows in a card is still going to yield acceptable end user experience performance-wise.
@Jose_Rojas you may need to handle your scheduling external to Domo if you have a snowflake procedure that needs to finish successfully BEFORE you ingest data into Domo. You might look at using Python to automate testing "did my snowflake procedure finish? if yes trigger Domo dataset execution."
Totally different use case, but here's an example of how you might build the LOOP structure.
Re: Where do Cloned Beast Modes Come From?
@zcameron this might be something for your team?
@James_Dougherty Domo has ... a handful of quiet releases and sometimes doesn't update the documentation to reflect updated language in the product.
I think it's important to consider how Beast Modes can be created / duplicated (and then test and you'll figure it out!)
1) a beast mode can be duplicated if it exists only in the card (i.e. not "shared to dataset") and then you duplicate the card. For sure that will create a new entry for the beast mode in beast mode manager because that beast mode is tied to that card. i'm unsure if it would have the language of "cloned" or not.
2) a beast mode can be duplicated if you duplicate the dashboard (and in the same process duplicate the card). it is unclear to me what impact it would have on language in beast mode manager.
3) if you go to the data center and move a card from one dataset to another (or do the same in analyzer), Analyzer will try to duplicate the beast modes from your card on that new dataset (it is unclear to me, test it and let us know! -- whether Analyzer will only duplicate the fields actually in use on the card or ALL the beast modes in the card that are NOT shared to the dataset, or ALL the beast modes including those shared to the dataset).
Hope that helps give a framework for your investigagtion..
Re: How to append based on new IDs only - not upsert
@JunkDoom given that you are describing ingesting Transactions into Domo, I would strongly recommend you investigate using Partitions instead of UPSERT.
UPSERT works well when you're uploading a massive Customer, Product (or similar) table where you have no idea when a particular Customer_ID or SKU might be updated.
Partition is the preferred ingest method on transactional data because you could (as you say) upload all activity that was created in the last 7 days and partition on the creation_date column (or whatever's appropriate.
While UPSERT might sound easier, the downside is processing, for each row i want to insert into DOMO i'd have to check if the transaction_id exists. Keeping in mind that the data is stored in a flat file, that search grows increasingly expensive as your data volume increases (more values to check) whereas with Partitioning i just have to answer "does this volume (date) exist? if yes, discard the existing date and replace, if no, create a new volume"
hope that helps.
Re: Connector Deprecation Announcement - Amazon Marketplace Web Service (MWS)
@Tclark07 it seems like connector usage would be an attribute of DomoStats which Domo Engineering should have access to for all customers right?
I know we wish everyone would log in to Dojo, but we know that's not the case. Hopefully Domo Support could partner with CSMs to push an email to the Major Domos of each impacted account?
If possible, how can I call a Stored Procedure or Function?
I am converting some dashboard in Tableau to DOMO and have run in to some obvious differences between the two. I'm trying to figure out how to pass a user selected field from DOMO to a Stored Procedure or Function as an argument. Right now I am reading in the entire table of xx million rows and would like to be able to constrain the data as the SP was designed. I see a parameter option field but can't find any real documentation as to how to use it...if this is what it can be used for.
Thank you
Re: Find most recent transaction - Dataset View
@swagner why didn't you @ mention me? sorry so late to the party!
sum(sum(1)) over ( partition by branch, item order by receipt date desc)
shoudl work i believe.
Re: Joining 2 datasets based on between condition.
Product Feedback / IDEA added here -- https://dojo.domo.com/main/discussion/55706/join-on-like-and-between-in-magic-2-0/p1?new=1
Dataset/Card Certification History
Hello,
I was wondering if there is any location in Domo where one can go to to view the history of a dataset and its certification status history. For example I have Dataset A and it is currently certified but a change was made in the ETL and it now has an expired certification. I now need to resubmit the certification for it. Is there anything like the table below?
Jmoreno