JosephMeyers Domo Employee

Sorry for the delay on this one. It looks like you have an open object storing the dataset row and then you are trying to reference a child of that open object for the email address. Is that correct? Unfortunately you cannot directly reference a child of an open object. I think there's an issue where it looks like you can.…

You usually do not directly write to datasets from custom apps, only query. Endpoints that begin with /api are also not available to custom apps. For documentation on custom apps endpoints look here - https://developer.domo.com/portal/8ba9aedad3679-ap-is#app-framework-apis Custom apps were designed to use AppDB and then,…

You cannot sync to a dataset without a schema.

PDP is for datasets not collections. Are you referring to document level security? To be able to write to the collection you would need to grant write documents permission on that collection to the users or groups or share permissions directly to the app instance and then share the app card to the users or groups you want.…

Which version of sendEmail are you using. There was a recent bug with one of the versions that has since been fixed.

Are you querying the dataset in this workflow or just trying to put the column names in directly? Can you share more details of exactly what you are doing in your workflow and what specifically isn't working? I feel like I don't have enough information.

You are passing IDs into a field expecting email addresses. Are these IDs user IDs within Domo? If so you will want to convert those IDs into the person type using the DOMO Entity Conversion package and then passing those into the sendEmail function as personRecipients.

You can update your schema in AppDB Admin and the manifest file. If you just update in AppDB Admin the manifest will take precedence whenever you make a new card from the design or push a new design version so it's recommended to do it in the manifest for permanent changes.

Yes, that number is the file id in Domo that results from using the Domo Files API

Are you referencing the Send Email Code Engine function? That attachment field is expecting the file id from the Domo Files API. Trying to locate documentation for that.

Domo has a Files API but it is not available in Bricks. https://developer.domo.com/portal/eeoadx67i6h46-files-api

Great that you were able to figure it out. I'll pass along the suggestion to the custom apps team. Most of the custom app documentation can be found at developer.domo.com but here's a link directly to the permissions information https://developer.domo.com/portal/1l1fm2g0sfm69-app-db-api#collection-level-security

It is not a grant on a role and you shouldn't need to edit the role. It is the permission on the collection. When you user tries to submit is there any error in the network tab? You can see this by enabling the devtools on the browser.

Both have been discussed and the plan is to be more like Publish and have an auto renewal system.

Open the dev tools for your browser and see if there is an error in the network tab when you click the submit button. Most likely it's a permission issue. Permissions can be set for Users, Groups, and Custom Apps. Any can be used for what you want but normally we rely on the Custom App permissions and then share the Custom…

Short answer - yes. Long answer - I am going to make some assumptions based on the default or more common ways different customer make custom apps in answering this and hopefully it lines up to what you are doing. When you say "submit new values into the table" I am going to assume you are storing that values in an AppDB…

The hotfix has been released and your workflows should behave as expected again.

Hey NateBI I got your ticket and figured out what the issue is. I've sent a response back to the Support team but am posting here so other know what is happening. Unfortunately, we have a bug where editing a start parameter is only saving changes to the displayName and this causes a missmatch between the display and what…

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