Best Of
Re: Recommendation: Connecting to Vertex
Hi @swagner
Looks like you might be able to use their GetFile end point to download a file from the URL however I haven’t use this product so that’s going solely off the documentation you provided. You can start there but you may need to bring in a consultant or someone more technical to complete this connection.
Re: Recommendation: Connecting to Vertex
@swagner this would be a 'usual suspects' type question if you asked a TAM.
Can Vertex automate emailing to you? (email connector)
can Vertex set up an automated file drop? (FTP, Amazon S3 or similar storage)?
I didn't look closlely at the documentation, but it sounds like Vertex provide a CLI (a cli presumably would allow you to gerneate a CSV locally on your machine which you could then ingest via Workbench.)
Re: User access levels for drill path layers
@serendipity if it were my requirement, I would have two separate cards for two different audiences. (AND still apply PDP as necessary).
Also, check in with your CSM, I believe Domo were working on column based PDP but I don't know how far they got on that.
Re: User access levels for drill path layers
technically, @GrantSmith and @ST_-Superman-_ are correct, but you do still have options / hacks.
1) build your initial card on a dataset view of aggregated data. apply PDP policies as appropriate.
2) when you create a drill path, you can reference the original dataset, OR point to a completely different dataset. Create a second DSV at a second layer of aggregation as appropriate, and again, control PDP. you can choose to allow Group A and Group B to see DSV 2 but NOT Group C.
3) when you create a drill path you can decide whether or now you allow drill down to the row level, or if drilling stops on a card. depending on desired outcome that can make the creation of a separate DSV superflouous.
Side note. this gets messy fast. usually people assume a card will drill to the same dataset ... when it doesn't then you get problems when you migrate to a new dataset or need to start maintaining beast modes in two places... but it works.
Re: User access levels for drill path layers
Hi @serendipity
@ST_-Superman-_ is correct. This functionality doesn’t exist currently especially since you’re wanting to conditionally trigger the drill path action based on your data. I’d recommend putting in a feature request for this type of functionality. The only possibility I would see is to utilize PDP to restrict access to the columns in the drill path but for your group C it would still allow access to the drill path but it would be empty.
Re: How to show top 10 contributors in any dimension field?
Hi @Kumar619
on your data table in analyzer there is a text box you can enter a number which will restrict the number or records displayed. You can sort by your metric and it will then display the top X number of records
Re: bulk updates to cards
Hi @akshayaviswanathan Simple answer - @Sam1 is correct... no. There is no bulk update
technical And complex answer:
Utilize the Java CLI to export your card definitions as JSON (backup-card command). Write a script to clean these files to remove the filter from the JSON definition Restore the cards from the updated JSON using the CLI and the restore-card command
If you go this route I’d recommend keeping an original backup of the cards.
Re: Set goals in ETL
APPEND your data instead of JOINing it.
Re: DOMO Rank System
Hi @user063136
You just need to add a partition to your window function to calculate the rank within each specific month.
RANK() OVER (PARTITION BY YEAR(`date`), MONTH(`date`) ORDER BY COUNT(`Certificate #) desc)
Re: DOMO Rank System
i think your result is correct even though it's not what you want.
start with a table card before you do a pivot table.
sort your card by year, month, count(cert) desc in your
validate whether your original rank() is giving the correct result. if not, try
sum(min(1)) over (partition by MONTH(`EventDt`),YEAR(`EventDt`) order by sum(1) desc )