Add custom fields to a data subset

RE: Add custom fields to a data subset

ManuelHTG — Wed, 19 Feb 2020 09:20:21 GMT

It is not a very good approach or practice to do that, because any change that you would do on the CDT would not be reflected on your expression rule. It would be much better to add those custom fields on the CDT. In general, what you are suggesting is not a good practice.

Anyways, the solution from Evan Rust would solve your problem.You don't need though to create a second CDT to cast, you can directly provide the structure.

this would give you a dictionary with the structure with id, name and ranking (always 2)

load(

local!student: rule!APP_QE_getStudent(id:null).data,

{

a!forEach(

items: local!student,

expression{

id: fv!item.id,

name: fv!item.name,

ranking: 2


}


)


}


)

RE: Add custom fields to a data subset

Robert Shankin — Wed, 19 Feb 2020 00:09:07 GMT

Maybe this plugin will help you

https://community.appian.com/b/appmarket/posts/cdt-manipulation

RE: Add custom fields to a data subset

Evan Rust — Tue, 18 Feb 2020 22:22:13 GMT

If you already have a CDT that maps to that table, you can create a second helper CDT that does not map to any table (i.e. do not publish in a data store), but that has all of the same fields plus an additional field that you use for your "custom value".

Then, in your expression rule you can call a!forEach and use a type constructor to build the CDT you're looking to build.

a!forEach(

items:local!myItems /*this is the result of some query you did to grab the data from the table*/

expression:type!mySecondCDT(

field1:local!myItems.field1

fieldN:local!myItems.fieldN

customField:1234 /*put whatever you want here*/

)

Then if you need this in a datasubset type, just use todatasubset() over it.