Errors running integrations since using Advanced Security

[Luvsql]

I was modifying a user class yesterday to remove windows from routines, utilities etc. in order to prepare for version 8's removal of palettes. Today, no users in that class can run integrations (errors are unknown Dynamics subtype 25968 or 25710) and it fails on every receivables transaction. On the same machine, if I log in as another user that is not a member of that class, it runs fine.


From what I see in TK, a third party's alternate window could cause the problem, but according the security setup of the class and that user, they do not have access to any of the Project Accounting windows, thus is using the standard GP windows. The user has no problem manually entering the invoice.

Why would modifications to a user's class in advanced security (simply unmarking window access) stop integrations from working?

 

[winthropdc]

I doubt that this is actually related to Advanced Security.

When you run Integration manager it overrides security so that it uses the original window rather than any alternate windows. This is regardless of what security says.

I sounds like a third party product, possible Project, is expecting the alternate windows to be used. Its triggers are firing and expecting to find the additional project fields on the window, but are failing due to the fact that the fields are not there.

Please confirm that the Security records are actually pointing to the original version of the window. This should be enough to tell any third party products that their window is not being used and if they are programmed correctly, the triggers will abort.

I know all code that I write with alternate windows, checks the security table and sets a flag to tell my triggers if the alternate is in use, but when IM overrides security, reading the security table produces incorrect results.

If you still get problems after changing the security, you can use Tools >> Customisation >> Customisation Status to temporarily disable triggers for the offending third party product. I would also let the developers know if you had to manually disable their triggers.

David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[Luvsql]

Yes, I have verified that in Adv Security, under that user and that class, that Great Plains is chosen as the window for all the sales windows (says the same in the regular security window). No other class has this issue and it was fine on Thursday (modified the class on Friday with Adv Security). This user has been able to run integrations for 1.5 years. When I change her class, she is able to use integration manager.

 

[Luvsql]

3 other users in the same class cannot run integrations (same exact error). I had to create a new user class with regular security and now they can run them. It IS adv security.

 

[winthropdc]

I would still have to disagree. If you made the same security changes with the standard class security window it would have the same affect as if you made the changes with Advanced Security... with the added "bonus" that any user level changes would be overwritten when you roll down the class.

Advanced Security is just a nicer interface into the standard security system, any changes made in either interface affect the same security tables.

What changes did you make to the class on that fateful Friday? Whatever those changes were, they are the cause of your issues.

Make the same changes with Standard Security and you will see the same issue.

PS: Please note that if granting security back to a resources, Advanced Security does have the option to grant access to the alternate and/or modified version by default (check the Grant Security Options in Advanced Security). Standard Security always grants back to the original window.

David Musgrave
Senior Development Consultant
MBS Services - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[Luvsql]

I modified my new class using Great Plains' user class setup (ie removing all the windows within sales except for a couple that they should have access to) and they can still run integrations.