Testing a developer's application with version 6.0 of Dynamics and eEnterprise can be slightly different then previous versions. The Explorer/Advanced Lookups product now installs by default, and therefore all users are automatically granted security access to the Advanced Lookup windows, which are Alternate Dynamics windows found in the Explorer dictionary. This can pose a major problem for Test Mode debugging because all of the Lookup windows are now being looked for in a dictionary that does not exist when working in Test Mode.
To get around this issue, developers should add the following line to their DEX.INI file in order to create users with no Security set to the Explorer product:
AdvLookups=FALSE
When a user has this setting in their DEX.INI file, no Security records will be created for the Explorer product as a user is granted access to a company within the User/Company Access window. A new user can now be created specifically for Test Mode that will allow the old style lookups to open. Note that these windows will not have the new User Interface.
It is also very important to test your integrations thoroughly in runtime with the new lookups in the Explorer product. This is the way that every 6.0 user will have their environment setup to use, so it is critical that your application runs well with the lookups from the Explorer product.
This article was TechKnowledge Document ID:18766
The issue that is described in the Issue section does not apply to Microsoft Dynamics GP 10.0.
To get around this issue, developers should add the following line to their DEX.INI file in order to create users with no Security set to the Explorer product:
AdvLookups=FALSE
When a user has this setting in their DEX.INI file, no Security records will be created for the Explorer product as a user is granted access to a company within the User/Company Access window. A new user can now be created specifically for Test Mode that will allow the old style lookups to open. Note that these windows will not have the new User Interface.
It is also very important to test your integrations thoroughly in runtime with the new lookups in the Explorer product. This is the way that every 6.0 user will have their environment setup to use, so it is critical that your application runs well with the lookups from the Explorer product.
This article was TechKnowledge Document ID:18766
The issue that is described in the Issue section does not apply to Microsoft Dynamics GP 10.0.