Saturday, June 28, 2014

Dynamics GP Community is under attack!

It seems our community is under spam attack! It is getting spammed by few LOVE Specialists! I would kindly ask for users who has outstanding questions to “repost” their questions once Microsoft folks resolves this attack!

I feel like CAPTCHA will be added soon to the community to avoid such spammers and also to annoy users!


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Analytical Accounting vs. Multidimensional Analysis

In earlier Dynamics GP versions, we used to use a module called MDA to manage our accounts dimensions and reduce the size of the chart of accounts, the module is very stable and works perfectly but with limited functionalities, when the Analytical Accounting was introduced, this module was retired and was no longer enhanced by Microsoft.

Personally, I been fighting with Analytical Accounting issues for many years now, I can count free hours spent to correct journals at the database level that unjustifiably corrupted and was not linked to the correct figures, which makes it a little bit annoying.

A couple of days back I seen a “conspiracy” being prepared between GP MVPs (including me!) against the Analytical Accounting pushing hard to get the MDA module back to track and enhanced to compete the AA module.

Frank has created the Connect request and we all voted to get this done, we need your help getting this ranked to the top of the list and to be considered in the very near release:

https://connect.microsoft.com/dynamicssuggestions/feedback/details/907907/bring-mda-back-to-dynamics-gp


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Thursday, June 5, 2014

Dynamics GP 2013 - Web Client Only Users & Active Directory Integration (LDAP)

This morning I been thinking about the new security structure for Dynamics GP web-client user who does not have SQL Users, and how these users will interact with SQL Server, I had to go through this as I have a client who’s running a very strict policy in granting SQL permissions for domain users.

Getting through this, I have created few users with multiple scenarios as below:

  1. The first user linked to domain account called that “TEST1”, but didn’t check “Web Client user only (no SQL Server Account)”
  2. The second user linked to domain account called that “TEST2”, and checked the “Web Client user only (no SQL Server Account)” option.

I have noticed that the first case created an “SQL User Account” called “TEST1” and didn’t granted the domain user any access to the database, and the second didn’t create any users which been a mystery to me understanding which user will be used to access the SQL Server!

To test this I have modified the GL00100 table and added a new column called “UserName” –this is for testing only, you cannot do this on GP tables!- and set the default value for this column to be “SUSER_SNAME()” function which returns the user who’s currently logged in and started my testing by creating new accounts!

Logged in by TEST1 to the web client and created a new account, the result was somehow wired, the user who was recorded was “DYNSA”

image

Logged in by TEST2 to the web client and created a new account, the result was the same, the user who was recorded was “DYNSA” as well.

Then logged in but selected “SQL Authentication” option from the login page:

image

The result was as expected, the logged in user was “TEST1”!

Now it been clear, all windows authentication users will be using one account to access the SQL, the login is the one you specified during the installation of the web client, so if you been counting on the user who is currently logged in in your customizations you might need to review your code!

Hope that helps giving you a good understanding to the new security process.


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Dynamics GP 2013 R2 upgrade: The following SQL statement produced an error: exec wfDeployClrAssemblies

During the upgrade process to Dynamics GP 2013 R2 with one of my customers we got the error in the subject, the issue is with dropping one of the SQL level Assemblies called “System.DirectoryServices” that been used by “Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine”.

The "System.DirectoryServices" assembly is being used by the Workflow module in Dynamics GP, if you have workflow installed you will not be able to drop this reference as you will be having another assembly depending on this and the other assembly is being used by 7 functions and stored procedures.

This assembly basically is used to connect your active directory and get the needed details that are being used by the system, dropping all these objects is safe as the upgrade process will automatically create them back for you.

To resolve the issue, first find the following functions and stored procedures, right click them one by one and hit drop:

image

Go to DYNAMICS database and navigate “Programmability>> Assemblies” and find “Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine”, right click the assembly and hit drop and then drop “System.DirectoryServices”:

image

Reinitiate Dynamics GP Utilities and and the upgrade will proceed safely, don’t worry about the deleted objects as the upgrade will recreate them all.

Hope that this helps.


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Update Currency Index field across all database

You might need to change the currency index for one of your currencies, I needed this during a consolidation project for multiple DYNAMICS databases and needed to change the currency index field for all company tables, take a look into the below script, I have used the “Information_Schema” to get all columns that are called “CURRNIDX” and updated these using SQL Cursor, considering that I taking a backup for each table before doing the operation:

DECLARE @Statement VARCHAR(8000)
DECLARE @TABLENAME VARCHAR(500)
DECLARE CURR Cursor FOR
SELECT TABLE_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE COLUMN_NAME = 'CURRNIDX' AND COLUMN_DEFAULT IS NOT NULL
OPEN CURR
FETCH NEXT FROM CURR INTO @TABLENAME
WHILE @@FETCH_STATUS = 0
BEGIN
SET @Statement = 'SELECT * INTO ' + @TABLENAME + '_BAK FROM ' + @TABLENAME
EXEC (@Statement)

SET @Statement = 'UPDATE ' + @TABLENAME + ' SET CURRNIDX = [NEW CURRENCY ID] WHERE CURRNIDX = [OLD CURRENCY ID]'
EXEC (@Statement)

FETCH NEXT FROM CURR INTO @TABLENAME
END
CLOSE CURR
DEALLOCATE CURR




Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Dynamics GP 2013 R2 – New User Maintenance

I liked the new active directory utilization for GP 2013 R2! take a look how does it look like now:

image


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Currency Symbol is incorrect for some GP forms

After updating the currency index field across all database, one of the users has reported that currency symbol does not match the functional currency symbol defined in the currency setup, and for some screens multiple currencies are shown as below:

image

After looking for this I have found this in MC40000 table, the Currency ID field represents the correct functional currency but the index was referring to another currency, updating the currency index field fixed the issue.


Regards,

--
Mohammad R. Daoud MVP - MCT
MCP, MCBMSP, MCTS, MCBMSS
+962 - 79 - 999 65 85
me@mohdaoud.com
http://www.di.jo

Related Posts:

Related Posts with Thumbnails