MarkSnodgrass Coach

@gbrown Form Builder is pretty basic and doesn't have any barcode scanning or QR code functionality, to my knowledge.

I have not experienced that issue. If you can replicate the issue with the user, I would do a screen recording of them submitting the form and then show that the dataset still doesn't show the submission and then sending that recording to Domo support as a ticket.

I would check in your data center to see if there is another responses dataset with a very similar name. Depending on how your form viewer was created, you can have multiple response datasets. It's possible the other user's entries are going in that other dataset. You can merge them together using the Append tile in Magic…

@gbrown if you are talking about viewing past submissions within the form viewer app, you have to configure that in the form builder configuration. In Form Builder, click on the 3 dots next to your form and click Edit. Then select "Allow previous submissions to be viewed". You can also allow previous submissions to be…

If you really wanted to generate the name of the month and year as text in your ETL, you can use the formula tile to do this. Your formula would look like this: DATE_FORMAT(`ActiveDate`,'%M %Y') However, if you leave the date as an actual date, in Analyzer, you can use the custom date format option in the field.…

yes, you can use the HTML table card to display this. You would create a beast mode that has the necessary HTML code to display the image, like this: CONCAT('<img src="',`Profile Picture URL`,'" style="width:128px;height:128px"></>') In this example, the full URL to the image is in the field called Profile Picture URL, but…

@Tina_Alpaca I created a video on how to do this in Magic ETL. You can watch it here: https://www.youtube.com/watch?v=9iNpzSL5V6U Hope this helps.

You are on the right track. I use form builder/viewer and here is what the main part of my ETL looks like that gets the data structured like you want. I first filter to submitted entries by filtering to where submitted = true. This eliminates where people started filling it out, but then abandoned it. The select columns…

I think you can do this using the variable feature. If you haven't played around with that yet, here is a demonstration of it that was just done today. https://www.youtube.com/live/ZCQwiBq8PHc?feature=share There are some other introductory videos that are worth watching as well.

Unfortunately, color rules are pretty limited and you won't be able to do what you want to do. I would suggest looking at the bullet chart for this. It will put a small line at your target value and will make it easy to see when your appointments are above or below the target line.

I would suggest using the variables feature to build this functionality. You can use the radio button control in the variable to have your different options that can be selected. Then, build a beast mode that would perform the correct date operation based on the variable selected using case statements. Then, drag this into…

@Canioagain the formula shows up in the formula tile in Magic ETL. For whatever reason, the beast mode editor in Analyzer doesn't show as extensive list of functions, but 95% of the functions you see in the formula tile in Magic ETL will also work in the Beast Mode Analyzer.

Ahh... I think I see the issue. Put your actual event date field in your sorting field and not the beast mode formatted field. I failed to notice in my own configuration that I have the actual date field in the sorting. Sorry I didn't catch that earlier.

That is pretty strange. Mine went pretty smoothly. I would try toggling the sort order and see if that shakes it loose. Sometimes, saving and closing the card will cause it to actually render correctly. Also, I noticed in the first screenshot, there was no sort order, so it is just grabbing the date by how the data is…

Are you saying that if an alarm id has a row that has Lost Connectivity and Disregard, you not only want to exclude that row, but also all rows with that same alarm id? If so, you won't be able to do this in a beast mode. You will need to do this in Magic ETL. You would filter to the records you want to exclude and then do…

@Zel you're close. You have the when correct, you just need to your then and else to be like's Stuck's. Like this: case when `Alarm Description` = 'Lost Connectivity' AND `alarm action` = 'Disregard' then 'Exclude' ELSE 'Include' END Drag this beast mode into your filters and filter to include or exclude, depending on what…

I would check your filters or your date range to see if something is keeping it. You can also switch to a table card and see what date is at the bottom. Posting a screenshot of what your analyzer looks like might help me troubleshoot.

I would check what is in your sorting properties. My change value options just had reverse color direction checked, which was just a remnant from a prior version of the card and wouldn't apply to this.

Create a beast mode that uses the date format function to format your date field in the format you want. Something like this: DATE_FORMAT(`transactiondate`, '%b %Y') Put this field in your category and then put a constant value in your values and choose any aggregation type. (You can even make a beast mode that has a value…

@charles Ha! Glad it worked for you. If you mark the answer as accepted, that will help others in the community that may run into a problem like this in the future.

If you are using the bar chart, you can use these chart properties to do it: Drag your metric field that is determining your "top" people into the Sorting field and sort by descending. Next, in the General Chart Properties: Set Sort on Totals and Descending Set Maximum Items to 5 Select Hide Other Bard

@charles It looks as though your calendar_shipDT is really just determined by looking at the schedule_ShipDT and seeing which day of the week it is and making the calendar_shipDT be the appropriate Wednesday. Here is what I put together that would accomplish this: CASE /* if the day of week of the schedule ship date is…

You can do this by using the rank window function in a beast mode and then adding it to the filter to filter where rank is less than or equal to 5. RANK() OVER (PARTITION BY WEEKOFYEAR(`date`) ORDER BY SUM(`metricfield`) DESC) If you don't have window functions for beast modes turned on in your instance, you will need to…

@Shwane when your string has an unknown amount of phrases you are looking for, you are going to need to use Magic ETL to break it up. I created a video on how to do this. In my case, I am looking for spaces, so you will need to change that and look for the hashtag, potentially. Here is a link to the video:…

Use the CASE statement to do this: CASE WHEN TRIM(LOWER(`email1`)) = TRIM(LOWER(`email2`)) THEN 'Match' ELSE 'No Match' END Using TRIM and LOWER will also help to ensure that it evaluates properly.

Sounds like you have a pretty good handle on it. Have you already played around with the data label settings when you using the custom chart? You can have the value show on top of the cell or a tooltip field value. That might solve your data label issue if you haven't already tried this.

@Stuck I'm glad you have found my videos helpful for you. In this case, I don't think the custom chart is going to work for you as each square in your grid would need to be labeled and the data then has to match it and there would be not sorting capabilities. I wonder if the heat map chart type would work for you. I used a…

Domo added a Risk Heat Map card type a few months ago. Have you tried using it? Here's the KB article. https://domo-support.domo.com/s/article/7506837994007?language=en_US

Since you are sending this every Monday, you can use this beast mode and put it in your filters and then filter to Include. CASE when `date` >= DATE_SUB(CURRENT_DATE(), INTERVAL 14 day) and `date` < CURRENT_DATE() THEN 'Include' ELSE 'Exclude' END You would need to change date in my example to the actual date field in your…

@NateBI even if there are no conflicts, in the Rename To box, you can type whatever you want, so you can type in the tablename.columnname for each column. It is manual, but that is how you would accomplish what you want.