Clarification on a!writeToDataStoreEntity

can you please check the input of wrtieToDataStore Entity, wheather the input is having all 5 cloumns data before inserting the database ?

The intention is to update the data , not insert new records. I have the primary key and the additional 2 fields that are present in the grid columns.

for me the above code is working perfectly we are on 17.4 hotfix A

load(
local!pagingInfo: a!pagingInfo(
startIndex: 1,
batchSize: - 1
),
local!data: a!queryEntity(
entity: cons!MK_DSE_QUALIFICATION,
query: a!query(
selection: {
a!querySelection(
columns: {
a!queryColumn(
field: "skillName"
),
a!queryColumn(
field: "certifiedOn"
),
a!queryColumn(
field: "employeeID"
)
}
)
},
pagingInfo: local!pagingInfo
)
),
a!dashboardLayout(
contents: {
a!buttonArrayLayout(
buttons: a!buttonWidget(
label: "Save",
saveInto: {
a!writeToDataStoreEntity(
cons!MK_DSE_QUALIFICATION,
local!data.data
)
}
)
),
a!gridLayout(
label: local!data.data,
labelPosition: "ABOVE",
headerCells: {
a!gridLayoutHeaderCell(
label: "Header1",
showWhen: false()
),
a!gridLayoutHeaderCell(
label: "Header2"
),
a!gridLayoutHeaderCell(
label: "Header3"
)
},
columnConfigs: {},
rows: a!forEach(
items: local!data,
expression: {
a!gridRowLayout(
id: fv!item.expense_id,
contents: {
a!textField(
label: "expitem",
value: fv!item.skillName,
showWhen: false(),
saveInto: fv!item.skillName
),
a!textField(
label: "expitem1",
value: fv!item.employeeID,
saveInto: fv!item.employeeID
),
a!textField(
label: "expType",
value: fv!item.certifiedOn,
saveInto: fv!item.certifiedOn
)
}
)
}
),
selectionSaveInto: {},
validations: {},
shadeAlternateRows: true
)
}
)
)


Above code snippet is working for me , when i click on button it's updating the values

oh is it ? did you properly replicate the scenario ?

Are you sure it is not affecting the existing values in the table for other columns ?

Hi,
Has it been like this from older versions as well? The answer is Yes. I tried in 16.2 as well.
it inserts new rows instead of updating the existing ones-- Did you check your CDT has primary key mapped to the "expense_id"?

Had to create a minimal CDT to make it work as suggested above by mohamedt808. I think that is the way to go .

Hi chandolum, How many columns are there in your CDT? only three ?

Hi Nihar Ranjan Hota,

If your CDT has 5 fields and your are trying to query only 3 columns(using query selection). Now you tried to save the three columns to the ri or PV variable(assuming the variable of type CDT that has 5 columns), Here the other two columns will be saved as null. this is expected behavior. So we need to query all the columns or create a new cdt with only three columns and try to update that (I would suggest the first one query all the columns if you have less columns and does not impact performance)

Thanks Chandu !

Thanks Chandu !