Kanban - Workstream & "Added Sub-Workstream" Column in Project_Form

[jainnilesh]

Hello - As a part of localization of Kanban App user, we needed a child level "Sub-Workstream" to the parent "Workstream". 

Therefore, added a column "Sub-Workstream" in the database as shown below:

1. Project Form Workstream drop down:

Issue: When populating "Projects_Form", the Workstream drop down is giving duplicate entries as shown below: 

Question/Help: How can we remove the duplicate entries and just have unique workstream populate in the Projects_Form

2. Projects Form Sub-Workstream Drop Down:

Issue: While clicking on the "Sub-Workstream" drop down in the project form, it's showing the list of "Workstream" similar to the above snip and not Sub-worksteam as shown in the first attached snip. Please see below:

Question/Help: How can we show the list of "Sub-Workstream"  vs "Workstream" in Projects_Form.

Thanks for the help.

[Suvrutt_Gurjar]

Please take a look at the dependent dropdowns functionality.

Dependent drop-downs - AppSheet Help

[jainnilesh]

Thanks @Suvrutt_Gurjar  - 

It did fix issue - 1. Project Form Workstream drop down: When populating "Projects_Form", the Workstream drop down is giving duplicate entries. 

However, somehow it's not not showing up the child level "Sub-Workstream" despite enabling the column in the project form. See below:

Can you please help with this? Thanks

[Suvrutt_Gurjar]

[Sub-WorkStream] should show after the [Workstream] is selected.

Please take a look at the sample app Dependent Dropdowns - AppSheet

The [Country] is shown only after [Continent] is selected and [Document] is shown only after [Country] is selected. Both [Country] and [Document] are dependent dropdowns.

[jainnilesh]

Thanks @Suvrutt_Gurjar  - It did work but now giving me this error "Unable to add row to table 'Comments'. → Invalid request provided to AppSheet database"

How can we fix it?

[Suvrutt_Gurjar]

For this issue, please try the solution in the last post by @Fabian_Weller in the below post thread.

error message: "Unable to add row to table → Inva... - Page 2 - Google Cloud Community

[Steve]

I strongly recommend against using AppSheet Database. Consider using Google Sheets instead.

[Fabian_Weller]

Why @Steve ?

[Steve]

AppSheet Database started as an independent project outside of AppSheet and grafted on later. As a result, you have a wildly inconsistent pair of interfaces. I don't find Database particularly intuitive, requiring me to learn an entirely new set of skills without any obvious benefit. Google Sheets is something I already know well, so it's easy for me to work with it. In fact, AppSheet's original target market was spreadsheet users who wanted to build an app atop their spreadsheets.

Because Database was not originally designed for AppSheet, there are some glaring gaps in its AppSheet integration, not the least of which is the inability to choose the key column! No virtual column keys, no composite keys, no using keys to enforce unique data values.

Labels must be defined in the database, which means labels cannot be virtual columns, which means no dynamic labels.

Databases appear to have many more limitations than Sheets for tables and rows, but oddly suffer from some of the same performance constraints that Sheets do.

Configuring and connecting a worksheet is much simpler than configuring and connecting a Database table. With a worksheet, there is very little configuration of the worksheet needed: just add columns and their headers. Everything else is done in the app editor. But with Database, there's so much back and forth to configure columns in Database then back to the app editor to configure them more.

There have been numerous posts here about odd behavior using Database that disappeared once switched to Sheets.

Why might you see Database as a compelling option, @Fabian_Weller?

[Fabian_Weller]

Thank you @Steve for the insights. I just started using Database for a personal app. Just out of curiosity. It really needs some time to learn.

[Suvrutt_Gurjar]

Hello @jainnilesh ,

May we request your updates on this post. Whether community suggestions worked for you or otherwise how you have solved it?

A conclusive post thread helps any future readers who are seeking similar solutions.

[jainnilesh]

@Suvrutt_Gurjar  - Apologies for the late reply. I worked out the solution. Please see below:

1. Add a new table and create a text column Sub-Workstream and Workstream  ref to Existing Workstream table (Mistake was adding column to Workstream table vs creating a new table)

2. Add Column to project table "Sub-Workstream" and ref it to the Sub-Workstream table that was created in step 1.

Done!

[Suvrutt_Gurjar]

Thank you @jainnilesh . Appreciate your revert.