Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Which function do we use to remove a particular field from a record before persisting it?
For example:
recordType!sampleRecord1( id: null, column1: A, column2: B, column3: C, column4: D, column5: E, column6: F, column7: G, column8: H, relationA: recordType!relationA( id: null, column1: A1, column2: B2, column3: C3 )) I want to remove the id field from both sampleRecord1 and relationA before persisting them.
Reason: The downstream database does not handle id: null well, but if the field is missing or field have a value, it works fine.
The output I want to save should be:
recordType!sampleRecord1( column1: A, column2: B, column3: C, column4: D, column5: E, column6: F, column7: G, column8: H, relationA: recordType!relationA( column1: A1, column2: B2, column3: C3 ))
Which function do we use to achieve this? i want to handle it dynamically rather mapping individual fields and then persisting .
Discussion posts and replies are publicly visible
This is a great find! For some reason I haven't had the need to do this before, since updating PK fields to be null in MySQL / MariaDB has worked ok when needing to copy a database row. But I just ran into an issue with a null PK record field with MS SQL Server, and running `remove` on the record field for the PK was an easy fix!
It is kind of considered undocumented given the text in the documentation for the remove() function only specifies integers. But hopefully that's just a quick doc update away, just like the same parameter for the index() function.