coz user can edit this manually in application,this app for recomendation for user only.but user aproved or not
1 Like
Okay, fair enough.
So if you want to set them via the API, you can follow my video and just make a minor change.
Once you have the mutation for each row, add an if-then-else column:
- If “Permintaan >0” is not empty, then Mutation column
And then use that column in the joined list. The rest of it will be exactly the same.
Right click on the table name in the Data Editor, and select Show API.
Choose the curl examples, and then Edit Rows.
You can copy the code from there, and remove the bits you don’t need.
See below to learn more:
1 Like
can you captured setting for collumn json data thanks
You can get it yourself by following the instructions I gave above, and it will give the exact values that you need for your table.
Thank you @Darren_Murphy For Sharing This,Its Work For ME
For some reason, the “delete row” does work on Relation with match multiple or a query. But if that works, why set column values wouldn t work just as fine. It s 2025 already and still doesn t work
Delete Row works with a query/multiple relation with regular Glide Tables.
It does not work with Big Tables.
Yes, but if that works perfectly, why “Set collumn values” or “Increment number” or any other wouldn’t work just as fine?
Because they are not supported. That’s why we created this feature request.
Let’s get this going!
WE REALLLY REALLY NEED THIS. For example, in my company app, I have materials connected via internal code. If someone modifies this code for example, is need to update it everywhere where it is stacked, like in every storage, every car, project where it was used etc. and even if it would take a few moments for it do change it everywhere, I wouldn’t mind. Because I won t have to go everywhere and modify it myself. and it can happen everywhere. I modify the name of the project in the main page? it needs to change it in the “reserved materials”, the transactions history and lots of other things. So yes, we need this asap. It would be sooooo helpful, better then just a game-changer. @Mark
This sounds like more of a database design issue. You should be writing the corresponding RowID everywhere and then using a relation/lookup to retrieve the internal code.
Same here. Write the Row ID for the project to the other tables, and then use a relation/lookup to retrieve the name. Names change, but Row IDs never do.
Change the value once and it’s automatically propagated everywhere else without the need to update multiple rows of data. That’s how I do it in my app. I have students and I always write the student RowID to all other tables instead of name. If the student name is changed, I don’t have to update the name in the other tables as the RowID doesn’t change, but the corresponding relation/lookup automatically pulls in the updated name. No need for any actions to update anything in the other tables. It just happens due to the relation/lookup.
2 Likes
I will think about redoing things with this, because I need to change it in lots of places. but still, we do need this thing implement
I agree, this feature request would be a good thing for certain use cases, but for your specific use case I would still use the RowID/Relation/Lookup method as it’s much less prone to error. If a Set Column action were to fail on one or several rows in one or multiple tables, then you start to risk a severe disconnect between data. Whereas a RowID/Relation/Lookup will work 100% of the time.
To be clear, I am all for this feature request, but I would selectively use it depending on the use case.
1 Like