Chris_Wolman Contributor

@TMonty0319 great news! How did you resolve the issue? Good to know for anyone who sees this thread in the future.

@TMonty0319 Do you have other beastmodes in the pivot table or summary number? What about null values in any of the columns?

Hi @gbrown , You will need a dataset in Domo that contains 2 columns. One column to be joined on and another column with a value. You will notice that there are 2 rows for 2 and 3 rows for 3 and so on. As you could imagine, this table can be quite large if you need a large number of rows to expand. Here is an example of…

There must be some other grouping on your table that is preventing the beastmode from aggregating. As @Jones01 called out. Do you have another column that is sorting or additional columns in your pivot table? If so, those either need to be aggregated, removed or included in the partition. My recommendation would be to…

Hello, Beastmodes are calculated at the row level and you are trying to calculate a value over multiple rows. You will need to use a window function with a partition or a fixed by function. Here is an example using a window function. Chris

Hi Barb, Yes, you can using something like the following: exec [yourStoredProcName] select * from [yourTableName] This will work in workbench or the MS SQL Server connector. You may have issues depending on how long it takes for the table to be produced. If this is a lengthy process, then you might be better off scheduling…

Another option could be an append job from workbench and a dataflow with a filter tile to exclude rows older than a certain date. It would depend on if you need to reload previous days data or not.

Thank you @marcel_luthi and @MichelleH . I believe the use of variables for start and end date along with identifying inventory movement is the solution that will allow us to calculate the beginning and ending inventories for the period any user selects.

Wouldn't the flex table give me the wrong beginning inventory because the 4/15/2023 row would be excluded when filtering 5/1-5/15 on the card?

Sure, here is an example of the data. The above illustration shows 10 units received on 4/15/2023. No sales for the item until 5/5/2023. The expected result is one row for Item A with beginning inventory = 10, ending inventory of 7, and sales of 3. This is why we are using a windowed function to get the beginning…

Hi @MichelleH , Variables will not work in this case because there may not be a row in the data for that start date. Example, user selects a start date of 5/1/2023 and end date of 5/15/2023. The earliest date available for the item is 5/5/2023. I would need the calculation to use the earliest date in this scenario which is…

@MichelleH how do I identify the max date selected on the card in the dataflow? This calculation needs to reflect the max date of the selected date on the card and calculate dynamically. The user may want to see the past 30 days or maybe the previous 3 months or any other range? I need to be able to select the on hand…

Thank you @RobSomers ! I will reach out to my CSM.

@ElliotGitter I would recommend opening a support case with Domo. We have well over 100 jobs running in WB with no issues. We average 2000+ job executions daily. You can look at the history page of your datasets in Domo and see some basic stats on what jobs are running and when. WB also has logs that can be reviewed. I…

I would be interested in knowing this as well. I could see why someone may want to see this on their cards but for me that would be the exception not the norm. Chris

Hello, Pressing F5 will force a refresh of the window. Sometimes this helps. You could also try restarting the workbench service if you have not restarted recently. If it is truly the host machine being underpowered than you would definitely benefit from upgrading or moving WB to a better machine. Chris

This is really needed. Alphabetical at a minimum is something that I could work with. I prefer the way page filtering works on the Domo app. IMO, filter cards are not easy to work with on the app.

Update in the event it helps someone else with this issue. By design the connector only supports date columns in the source table. Converting a datetime column in SQL will not work.

Thank you. I was hoping maybe someone on here had encountered the issue previously. I have a case open with support.

The answer is yes it can! My issue was that the Domo IP Addresses were not whitelisted for access to the server. The IP Address list can be found here - https://domohelp.domo.com/hc/en-us/articles/360043630093-Whitelisting-IP-Addresses-for-Connectors May be helpful for someone else in the future. Chris

@Ritwik - when a job is scheduled to run between specific hours then it appears to run on the hour. There is no option to say run at 5 minutes past the hour between these hours. @GrantSmith - Thanks. I remember utilizing windows task scheduler in WB4 for more advanced scheduling. That will most likely be the solution if I…

Hi @jaeW_at_Onyx , I do not see anywhere in the documentation how to change the start time of a job? In WB4 you could choose the start time of jobs so all of the jobs did not run at the exact same time. How can I schedule a job that runs every hour between 7pm and 3am to run at 5 minutes past the hour instead of on the…

Any update on this or a work around available? Thank you.

Thank you for the idea! The date and time is already a beast mode but I created another beast mode as a string for the axis and it allows the date selector to be used. Chris