GrantSmith Coach

DDX Bricks are pre-compiled Domo apps. Because of this the dataset names are pre-defined in the manifest file used to generate the bricks. These can't be changed in a DDX brick. If you want to go an additional level deeper in the development stack you can do a custom app which allows you to define the datasets and names…

I'd recommend logging a ticketed with Domo support for their development team to look into.

This hasn't been released to General Availability yet. I'm hoping it'll be released soon, maybe with the Domopalooza release. You may be able to reach out to your CSM to see if it's an available beta for you to have enabled in your instance.

I believe the ID should be unique. @NoahFinberg - can you confirm?

Create DDX Apps requires the Create DomoApps grant as well. The grant permissions window is unclear. Saving data from the app would require AppDB permissions as well.

This is likely caused by a missing common algorithm used to encrypt the traffic between the SFTP server and WB (they can't speak the same language). You may need to install other encryption algorithms on your SFTP server to allow WB to communicate. Domo Support may be able to tell you what encryption algorithms are…

Without seeing each of your bar values, I believe the chart line is taking an average of each percentage/bar in your chart, but the summary number is taking the percentage across the entire dataset.

Likely, you have multiple records for the same SalesOrderNo value so when it's doing it in aggregate it's doing the distinct count across all superintendents instead of adding each individual distinct count per individual superintendent.

Because your aggregation is within your case statement, it's getting treated differently. Try this instead: COUNT(DISTINCT CASE WHEN HdrParentItemCode = 'ZPUNCH' AND JT158_WTParent = 'Y' THEN sonum_wtnumber END) / COUNT(DISTINCT CASE WHEN JT158_WTParent = 'Y' THEN SalesOrderNo END)

Looks like you're using %22 which is a " character which would end your HREF property on your A tag. Try using single quotes instead (%27)

If you right click on the page and then inspect. Click on the network tab. Then reload the page and see if any of the requests come back with an error / red. This may give you more information into why it's failing to allow you to edit the brick.

How you solve this will depend on your dataset and if you're recording individual days if they pass or fail or just the failures. Do you have some sample anonymized data to help illustrate this for us?

I don't believe this is possible within a Brick due to the security concerns around the storage and usage of account credentials.

The issue is that your metadata variable is undefined and you need to handle the Promise. I'd try to do something like: domo.get(metadataQuery, {format: 'array-of-arrays' }).then(function proces_metadata(metadata) { fields1 = metadata.columns … domo.get(query1).then(…) } )

Are you doing a platform embed? There should be a profile icon in the upper right for you to log out of. I know you can access the logout link directly: https://{customer}.domo.com/auth/signout

I'd recommend calcluating the first date of the week and use that for your sorting. If you have a Date field you can do something like this: `Date` - INTERVAL (DAYOFWEEK(`Date`)-1) DAY This will return the Sunday of the week.

You can configure cards on dashboards to link to other objects within Domo so you can have them link to another dashboard. If you're wanting to go to a specific section (like an HTML anchor tag) this isn't currently supported. Some cards do support HTML coding directly within them (table cards) such that you can have the…

There isn’t a simple way to ungzip the data coming back within the connector ide and domo doesn’t allow for external packages for security reasons. You’d likely need to write your own gzip function based off an existing gzip package

If you have one value per month you can utilize a LAG window function. I've written up about these here: Alternatively you can restructure your data so that you have a period type (Current, Last Month) and a specific value for your months then utilize some beast modes to calculate the difference. Here's another write up on…

There isn't an official way of doing this however you could attempt to monitor the network traffic for the API calls Domo is making and replicate those within a script.

Alternatively, you can use smart text either in the title or description of a card or use a text card with smart text to show when a dataset was last updated.

You should be able to ignore the fields parameter in your query and it should return all of the fields that are in your dataset.

You can use a filter tile with a formula and the CURRENT_DATE() function: `Date` < CURRENT_DATE() - 1

To clarify, the issue is that you're having is that your beast mode is always returning NULL now as the MONTH function returns a number 1-12 based on the month. MONTHNAME returns the name of the month. Instead of using a case statement to attempt to compare the value to the month names just use MONTH(`Offer Accepted`)

This is likely because you're sorting based on the Year first and also the month by name. You'll want to sort by the numerical version of the month first and then the year. You can use the MONTH function to get the month number. Alternatively you can use the LAST_DAY to get the last day of a month and sort on that instead…

You can't aggregate an aggregate in a beast mode unless you're attempting to use a window or fixed function. Also, you can't compare an individual value to the aggregate of that same value within the same beast mode. Again this can be resolved with a window or fixed function: COUNT(DISTINCT CASE WHEN `Start` >=…

Can you post some examples of your raw data before your replace text and also what your replace text tile settings look like? There may be a more programatic way of solving your problem with a regular expression.

You used to be able to do this with the CLI tool and specifically the backup command; however, it's since been deprecated per the documentation but you may be able to still utilize this > help backup backup: Performs a backup operation, to AWS S3, for all Domo entities of type <t>. backup -k <S3 Key> -s <S3 Secret> -b <S3…

Domo doesn't provide a way to set a default for a filter card on a page except for using the page filters. You may be able to set a default page filter as @MichelleH mentioned which should affect the embedded dashboard.

You could use the start date of the week as your date range so that you have a single week value like your week number but is an actual date. You can use a formula tile and a formula like: `date` - INTERVAL (DAYOFWEEK(`date`)+1) DAY Then you can group your data on this date to either take the min, max, sum or whatever…