Best Of
Re: Extended DataSet information on DOMOStats
This is a great idea. I think it would also be helpful to show the state of the dataset (Draft, Disabled, Non-queryable, etc.)

Re: View as user or view as role
100%.
Trust and a more positive user experience will come from our Dev team being able to catch authorization issues. Whether that’s seeing if PDP works correctly to have card/page access set correctly.
Re: Magic ETL Preview Single Tile / Run to Here
Love this idea!
Would also love to have all the heavy lifting of the front end run once and then be able to run a few tiles at the end to tweak things.
Re: CASE When order
- 1)
- I don't think that it's this BeastMode that's causing the data to split across columns, since you're summing it. It's probably the TEST column, which I assume is the same one as this discussion:
To quote myself from that discussion:
"One note of caution is that your current set-up won't work if you have multiple nmPerformers in your data. You either need to insure a single performer is filtered or include the performer as a column in your table."
2)
I've been following your work on this table for a few weeks, and I admire your tenacity, but I want to recommend a different approach. In general, I would recommend using BeastModes to do math on data that you already have in your table. You seem to be using BeastModes to add new data, which is not a sustainable way to store/update/view your data. Create small tables of these expenses and join them to your data before going to the analyzer and BeastModes. Then, if new expenses need to be added, you can add them to your table rather than having to manually add it to the BeastMode every time.
Re: Does Domo publish a list of new releases or version changes made to their APIs?
API documentation from Domo has been historically poor. You are using the OAuth API, which usually changes versions if there are significant changes. But, API development has also historically been disorganized and not well managed. There isn't a list of changes anywhere that I've found unfortunately. When these changes happen, I just fix them as quick as I can and move on. If you have something that cannot fail or have any downtime, I'd suggest not using the APIs.

Re: Join Multiple Input Data
You'll want to use the append tile instead if the structure of the data is the same. Append will add rows to the bottom of the other DataSet, without increasing columns. Joins is for joining on keys and will increase the number of columns you have. If you still need join, you just have to use multiple join tiles one after the other.

Re: Transfer Street Address to Geo Latitude and Longitude Using Python
Dear @Chuqi_D,
As far as I know, you can't directly call APIs through Domo's Magic ETL. You may use Jupyter Notebook within the Domo environment for that purpose. I tested your code, but it doesn’t seem to be working correctly. I'm investigating the issue and will update you if I find a solution.