JosephMeyers Domo Employee

Forms are currently not supported. The plan is to support them but no set timeline on when that will be. https://domo-support.domo.com/s/article/4403367344023?language=en_US#unsupported_items

Can you go to the function in Code Engine and click the arrow to test run it there? See if that works or provide the error information if it doesn't. Or you could also try again and get a fresh TOE on that error and I can take a look and see if that shows anything. From what you've explained it seems like you are doing…

Open the developer tools and get the message from the network tab when that toast pops up. That should help with diagnosing the issue. That or contact the support team and they can walk you through the troubleshooting.

We currently have a defect with the error messaging but will be happy to look at the logs. What type of cards are these? Can you please contact our Support team to a get a ticket logged and we can have the Sandbox team take a look for you.

Is it creating a new App Studio app every time there's a change in dev and you promote? What type of changes are you making in dev? If you are still running into this issue please file a ticket with our Support team and we can have the Sandbox team take a look at your specific issue.

Likely it's just that the Brick is using an older version of the domo.js library. I've passed this along to the team.

Private Embed and Programmatic Embed are different things. Grant is referring to Private Embed and the original question seems to be for Programmatic. It looks like there is an issue with the client id and secret. Here is some documentation on the subject - If you are still having trouble with it please have your Support…

Looks like you have discovered a defect. We should have a fix out for you later today. Sorry for the inconvenience.

You have to add it as a card.

Depends on how you added it. Did you use the options I mentioned earlier to add it to App Studio and it's still not working as expected?

Bricks are unique per app instance or in this case card. Adding an app creates a new instance of the design which with standard custom apps would show the same for each card. With Bricks, since they have customized settings and code stored unique to each app instance, a new instance would show the default state since none…

To add a Brick card to App Studio you will want to use the Card option in the CONTENT section and then ADD CONTENT > Add existing Card

Despite the similar names App Studio and Custom Apps are completely different things. App Studio is more like an advanced dashboarding tool that can have apps as part of it. Custom Apps information can be found here - There is also a beta for the Pro-Code editor which will let you edit and preview custom apps inside Domo.…

So sections by nature are intended to be separate pages. As far as customizable forms the forms themselves are not. It would have to be a custom app that is coded to display as a form. That would have to be fully custom code on your end though instead of something out of the box.

Bricks are restricted in public embed for security reasons. You could use a standard custom app to do the same thing but I would caution against putting something allowing any and all public user input out there.

I don't believe any have phone number type validation, signature question types or style changes to the title. Not sure exactly what you mean by sections within a single page but that may be possible. The Brick won't have any of that without you custom coding all of it but it is all technically doable as custom apps can be…

Form Builder and Form Viewer are custom apps that provide a system to create and submit forms. Builder can build and submit while Viewer is submit only from the forms built in builder. These use AppDB collections that sync to DataSets. These are considered legacy applications however and the plan is to replace them with…

Bricks usually have more than 1 DataSet by default just in case you need them. This is because Bricks don't have access to the manifest to add or remove wired items. As suggested, if you never need the sample datasets wire all datasets to your desired one(s) and then you should be safe to delete the unwanted datasets. It…

PDP policies work the same in apps as they do in cards. Are you referring to the PDP previewer? That does not currently support apps. It's just a filtered view based on the PDP policies.

Unfortunately, Custom Apps do not have an automatic way to see the dashboard name of the page they are on. They can usually see the ID however and, while not an elegant solution, you could make a lookup table with the names and IDs and use that.

It looks like you have a solution figured out but just chiming in to say you can't aggregate inside the fields section. Aggregates are a query param like sum=field1,field2 See -

The Quick Date filter does not support custom apps. EDIT - I guess I should get clarification. This section is for custom apps are you referring to those or are you looking for App Studio help which would be a different section?

Because of the parallel gate it will assign one form which will wait but then also go through the loop on the other path and assign the next person which will also wait and then loop and assign the next person and so on. Once the loop finishes it will end that path but the workflow itself is still in progress because it is…

There are probably other ways to do this but you would want your loop that goes through the list of persons to go into a parallel gate that has one path going to the form and a second path that re-enters your loop. This is a crude layout of kind of what you are looking to make: A more fleshed out workflow using only Global…

Yes, you can assign variables that are of the Person or Group type from that drop down.

Are you looking for something in App Studio or in a custom app? I know we use the term "app" a lot but they are different things and the solution is likely different depending on what you are trying to do.

Information on filtering can be found here

We recently made changes to allow for nulls where appropriate. We are working on either having the Global Functions handle nulls better or setting the ones that cannot handle nulls to not allow nulls. Hopefully that way situations like yours cannot happen. Thanks for the feedback.

I have some good news for you. We are releasing a beta soon for an in browser editor for custom apps. This will provide you with a better editing experience similar to what you have seen with Bricks and have all the templates you can currently get in Bricks. It also doesn't have the restrictions that Bricks have with…

The name in the start endpoint is the aliased name. When you edit the app you can see the alias names in the wiring screen.