Query database configuration .

RE: Query database configuration .

Mike Schmitt — Thu, 14 Apr 2022 15:11:28 GMT

That's not really relevant. If you have the table's primary key ID, you can query the current data in that row, update the value, and re-write it using WTDS. This is still true regardless of whether someone's looking at an interface that uses View data.

RE: Query database configuration .

dhavalp0001 — Thu, 14 Apr 2022 15:06:49 GMT

As I used view to display data on dashboard . When I edit data on dashboard it will save to database. So not all fields have come in view. That's why i use this query database to update data.

RE: Query database configuration .

Mike Schmitt — Thu, 14 Apr 2022 14:51:39 GMT

Note also that it's trivially easy to query the most recent version of a row, update just the desired field, and re-write that value - it won't update anything other than the value you updated. This is a little easier than Stewart's suggestion, in cases where it's not being done very much (and thus potentially impacting performance or risking conflicts).

RE: Query database configuration .

Stewart Burchell — Thu, 14 Apr 2022 14:47:05 GMT

You can create a CDT that only has the field(s) you want to update and the field that uniquely identifies the target row - a so-called "partial CDT" and then you can use the WTDS node as you would normally.

RE: Query database configuration .

dhavalp0001 — Thu, 14 Apr 2022 14:35:54 GMT

I want to update only few field in table not whole data so that's why i am using this query database service.

RE: Query database configuration .

Mike Schmitt — Thu, 14 Apr 2022 14:23:22 GMT

Is there any particular reason you're not using the Write to Data Store Entity node? The Query DB node is recommended to only be used sparingly and when there are absolutely no other options, as far as I know. The configuration is more difficult and more confusing (as you've experienced) and you won't find anywhere near as much support for it here.