I have an API set up in IRIS which is secured using an IRIS authentication service, so there is a bearer token being passed down in the request header.

I've already set Parameter HandleCorsRequest = 1; on the spec class and All the endpoints I am have (a mix of GET, POST, PATCH and DELETE) are working from postman without issue, the problem is when consuming from the web front-end and the preflight checks the browser instigates. Most of the endpoints work in the browser, but some are triggering the preflight (OPTIONS) check causing the CORS issue.

This is what I am seeing in the browser:-

Hello all,

If we have a global structured something like this:-

1. ^test(1)="Dave^Engineer"
2. ^test(2)="Bethan^Manager"
3. ^test(2,"transferred")="2024-01-04"
4. ^test(3)="James^Administrator"
5. ^test(4)="Sophia^Marketing Executive"
6. ^test(4,"transferred")="2023-11-20"

It is fairly straightforward to map, and from a reading perspective everything works fine, but when inserting/saving the "transferred" node is created even if the 'transferred' field is not set. Is there a way to populate the node only if the field mapped to it is set?

Thanks

Colin