JamesNewman wrote:We have a problem where the StaffID has been set to nullable on the GL_Transactions table, if we revert this back to its previous state on a temporary basis, will it cause other problems. We need to do this to keep another import interface working that cannot be changed before upgrading to the next version.
Hi James,
If you make the StaffID Column NOT NULLable on GL_Transactions then this may cause issues - we won't know unless we do all our regression testing with that schema change. I would have to assume it would cause issues. You can probably get away with the temporary removal of the foreign key constraint - if that is what is actually causing your issue (As Scott suggested) - but you might find reports or screen information becomes inconsistent as it may expect the StaffID on that table to be valid and thus joins to the HR_Staff table will cause records to be omitted.
The recommended action is to only insert into that table either with NULLs or a valid value. A trigger should be able to do that for your purposes.