Fix Dynamics GP scaling and font
size issues on high DPI displays
Save this text to a file called
"Scaling.reg".
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
"PreferExternalManifest"=dword:00000001
Once you have created the "reg" file, double click on it to import it into the Windows registry on the machine where Dynamics GP is installed.
Then save the below xml text to a file called Dynamics.exe.manifest.
<?xml version="1.0"
encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0"
xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32"
name="Microsoft.Windows.Common-Controls" version="6.0.0.0"
processorArchitecture="*" publicKeyToken="6595b64144ccf1df"
language="*">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32"
name="Microsoft.VC90.CRT" version="9.0.21022.8"
processorArchitecture="amd64"
publicKeyToken="1fc8b3b9a1e18e3b">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
<asmv3:application>
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
<ms_windowsSettings:dpiAware
xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
Then
copy your new Dynamics.exe.manifest file to the GP application directory where
the Dynamics.exe file is located.
(C:\Program Files (x86)\Microsoft Dynamics\GP2018)
After the Correction GP will appear Normal.
You can find the Audit Trail codes that are associated with the transactions for each module by going to the path below. The one that I have below is for Financials, if you would like to see it for other modules then just select a different module from the combo box and there you are.
2. Login as sa and export out all the reports one by one or all at once with the same name as a report (This helps in identifying the report), which will create a package file for each report. (Filename.Package)
3. Confirm all the reports are exported out with the above-mentioned extension.
4. Make a backup of reports.dic and rename it or completely move it to a separate folder
5. Log into GP and go to Microsoft Dynamics GPàToolsàCustomizeàReport writer
6. The above step will create a new report dictionary for you which you can verify, once verified
7. GoTo Microsoft Dynamics GPàToolsàCustomizeàCustomization Maintenance, you will not see your modified reports at this point.
8. Choose Import on the right-hand side of the reports menu and import all the reports that you exported out of GP one by one or all at once.
9. This will recreate your whole report dictionary with all the modified reports in there.
10. Just to make sure, please verify the security for these modified reports by going to Microsoft Dynamics GPàToolsàSetupàSystem
Navigation Lists in GP are pretty powerful but often ignored for just a few simple reasons. Either users are not aware of them, or they get errors when trying to open Navigation Lists, so they just give up and never circle back to them.
If you fall into the former group, Navigation Lists can be found by visiting a module within Microsoft Dynamics GP and looking in the left margin (Navigation Pane). Navigation Lists can save you tons of valuable time by performing many tasks right from within the list itself. For example, if you wanted to put a few vendors on ‘hold’, or approve multiple workflow documents at once, you could do this right from the list window.
“Focus Shawn! Tell us more on Navigation Lists in another blog, for today, we want to learn how to fix that pesky error!” Ok, Ok Onto the fix.
As I mentioned, if you have tried using Navigation Lists, you may have received an error – something like rsAccessDenied400The permissions granted to user ‘XXXX’ are insufficient for performing this operation. blah blah blah.
There is text for a link – I’m sure it does go ‘somewhere’ but the link is incomplete.
Oh well – either way, this error relates to the Reporting Services permissions from SQL Server. Why is this happening? Well, when opening a Navigation List, Business Analyzer (Think SSRS) wants to access a few KPI’s and you apparently do not have access to them! NOOOOO PROBLEMO!!!
You can either resolve your user access to those KPI’s or just turn off Business Analyzer. You can do this by clicking the Navigation List name (see my example below) and turning off Business Analyzer (CTRL+F2 will do the trick too!). This setting applies to that specific list, for the user making the change.
Easy. But wait. there are a lot of Navigation Lists, and that’s a painful workaround, for each user! No problem. Here is a script to turn off Navigation Lists for every user. Run this against your system database (mine is currently set as ‘Dynamics’). This script will turn off Business Analyzer for all users, for all lists, for all companies!
UPDATE DYNAMICS..SY07225 SET FactBoxVisible = 0
If at any time a user wants to use Business Analyzer, all they have to do is go into GP and check Business Analyzer for that list!
By default, any new Navigation List is going to be set to show Business Analyzer. This can be resolved by creating a simple trigger to update the FactBoxVisible setting to 0 after a new list is created. Run this script against your system database if you want new lists to automatically ‘hide’ the Business
Analyzer. Name it what you’d like
CREATE TRIGGER
dbo.disable_BA_On_Nav_Lists on dbo.SY07225 AFTER INSERT
AS
Update SY07225 SET FactBoxVisible = 0
GO
Of course, you could also resolve the security access to the reports if you want to use the KPI’s… IMHO, KPI’s in the lists take up too much space and slow things down a little – if I need the KPI, I’d rather access them directly through SSRS.
No comments:
Post a Comment