This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Chat App - form missing field

Posted on 03-29-2023 03:57 AM
ayates
Silver 2
Silver 2
Reply posted on --/--/---- --:-- AM

Hi folks --

I've built a very simple app that allows people to share URLs with a comment, and have those published into a Chat space. I've added a /slash command, that uses the same (system generated) form as the app, so people can share the URLs direct from Chat too.

However, the view in Chat is missing the 'comment' field. I checked through the settings, and realised that this field is marked as 'key' for the table. I switched the key to the URL field, and sure enough, 'comment' shows up, but URL is not there. In my app, both are required fields - which means the slash command always fails, because the user can't fill in both. 

Any ideas? Is this expected? The (web) app doesn't have the same behaviour.

Many thanks!

-- Andy

0 1 189
Topic Labels
0 Likes
1 REPLY 1

Posted on --/--/---- --:-- AM
rmsmeltz
Silver 1
Silver 1
Reply posted on --/--/---- --:-- AM

@ayates 

It sounds like the missing field in the Chat view may be related to the fact that the "Comment" field is marked as the key for the table. When a field is marked as the key, it becomes the primary identifier for the table and may affect the way that data is displayed in certain views.

Here are a few potential solutions:

  1. Try changing the key field to a different field that doesn't contain any required data. This may allow the "Comment" field to be displayed in the Chat view without causing any conflicts with the required URL field.

  2. Consider creating a separate table for the Chat view that includes only the necessary fields for sharing URLs and comments. This can help to simplify the data model and avoid any conflicts between required fields and key fields.

  3. If neither of the above solutions work, you may need to reach out to the AppSheet support team for further assistance. They can help you diagnose the issue and provide more targeted solutions based on the specifics of your app and data.

It's also worth noting that the behavior of the Chat view may be different from the web app view due to differences in the way that data is displayed and managed in those environments. If you're not able to find a solution using the above suggestions, you may need to experiment with different approaches to see what works best for your app and use case.