With CDTs I can do something like this to initialise a CDT with all fields set to blank/null
cast( 'type!{urn:com:appian:types}CustomType', {} )
Is anyone aware of a similar approach with records? Casting {}, null(), or a!map() to a record type just returns null
In this use case I won't know the field names to be able to use them. I only have the record type
**Edit: Adding more context
If the record type has fields A, B and c then each of those fields needs to be set with null/blank (which is what would happen with the CDT).
eg the value returned is recordType!CustomType(a: null, b: null, c: null)
Discussion posts and replies are publicly visible
Why is that important? What do you want to achieve?
Validation of payload from external systems before writing the data, eg if payload from external system doesn't match the record type / CDT being written then return a 400.With older apps that use CDTs, we can store the type #, then get the keys from a blank initialised CDT (using the cast method above) and compare it to the keys in the JSON payload. With records, it seems we'd need store all the record field names to be able to compare them, which makes it more difficult to manage in the long run if fields change with code changes.
OK. Thanks.