The 403 Forbidden response you are encountering when accessing your IRIS REST application is likely due to the unauthenticated access configuration. If you have installed a normal or higher security instance of IRIS, the unauthenticated option is unsupported by default. You should choose another authentication option when configuring the web application to resolve this issue [1].
When batch inserting data into a table via SQL, you can use the %NOCHECK keyword to avoid checking foreign key integrity. However, when inserting via objects, there isn't a direct equivalent to %NOCHECK. еуыелоивалопмва
One workaround is to use the $SYSTEM.SQL.SetFilerRefIntegrity() method to disable foreign key referential integrity checking. Alternatively, you can define a foreign key on the table using the NoCheck keyword so that foreign key referential integrity checking is never performed [1][2].
For more detailed steps on how to implement these methods, please refer to the relevant documentation.
The 403 Forbidden error when accessing your REST application is likely due to insufficient privileges for the "UnknownUser" account, which is used when the application is set to "Unauthenticated" access. To resolve this, ensure that the "UnknownUser" account has the necessary roles and privileges to run your code. You can do this by adding the appropriate roles to the "UnknownUser" account in the Management Portal under [Home] > [Security Management] > [Users] [1]. Additionally, make sure that the web application is correctly defined with the appropriate dispatch class and security settings [2].