Microsoft Dynamics GP 2016 R2 Feature of the Day -SmartList Favorite Protection

Enjoy your Microsoft Dynamics GP 2016 R2 Feature of the Day!

SmartList Favorite Protection

Microsoft Dynamics GP 2016 R2 Feature of the Day

Are you a Tridea client interested in installing Microsoft Dynamics GP 2016 R2?

Contact us first!  Tridea Partners 858.755.3700 or info@trideapartners.com

By Tridea Partners, Microsoft Dynamics Partner www.trideapartners.com

Read original post at: http://community.dynamics.com/gp/b/gpteamblog/default.aspx

Dynamics GP 2016 R2 Feature of the Day: SmartList Designer in Advanced Lookup

Enjoy your Microsoft Dynamics GP 2016 R2 Feature of the Day!

SmartList Designer in Advanced Lookup

GP 2016 R2 Smartlist Designer

Are you a Tridea client interested in installing Microsoft Dynamics GP 2016 R2?

Contact us first!  Tridea Partners 858.755.3700 or info@trideapartners.com

By Tridea Partners, Microsoft Dynamics Partner www.trideapartners.com

Read original post at: http://community.dynamics.com/gp/b/gpteamblog/default.aspx

Dynamics AX 2012 R3: Stopped Workflow Error

When working with different types of workflows in Microsoft Dynamics AX 2012, you may encounter a stopped workflow record with an error message detailing that AX ‘failed to create a session’.

AX 2012 R3 Stopped workflow error

The error message can be generated because the workflow is unable to assign the record to a user for review or approval.

To resolve this type of issue, the first step is to identify which user record is causing the issue. Because no user ID is mentioned in the error message, you can identify the user by first finding the step where the workflow stopped. In the Workflow history form, click the Tracking details tab (screenshot above) to identify the step in the Workflow activities pane which has the Workflow stopped error message.

Next, navigate to the workflow and open the workflow editor to determine if the workflow step is assigned to a user, user group, security role or hierarchy. If the step is assigned to a user, you can easily identify the user which is causing the issue. If the step is assigned to a user group, navigate to the ‘User group’ form [System administration>Common>Users>User groups] and click the Users tab for the user group to identify which users are assigned to the group. One or more of these users could be the cause of the issue. If the step is assigned to a security role, navigate to the ‘Assign users to roles’ form [System administration>Setup>Security>Assign users to roles] and select the role to identify which users are assigned to that security role. Again, it could be more than one user causing the issue. Lastly, if the assignment type is a hierarchy such as the managerial hierarchy, navigate to the Positions list page [Human resources>Common>Organization>Positions>Positions], filter on the worker who submitted the record to the workflow then pinpoint the position/worker the hierarchy would assign the record to based on the ‘Reports to’ field.

Once you have identified the user(s) the step is assigned to, verify that each user record is enabled, the user is assigned to the appropriate security roles and that the user record is associated with a worker record.

In the case I investigated recently, the approval step where the workflow stopped was assigned to a user group. One user in the group had been disabled in AX but the user was not removed from the user group. The workflow was attempting to assign the record to each user in the group. Because one user was not enabled, the workflow could not assign it to all users in the group which caused the workflow to stop at an approval step. Once the user was removed from the user group, the workflow was resumed and the record moved forward in the workflow as expected.

This post was written by Robin Ellsworth, AX Application Consultant at Tridea Partners. Tridea is a leading Microsoft Dynamics provider.

Microsoft Dynamics GP: Analytical Accounting and Integration Manager

One of the downfalls of Dynamics GP Analytical Accounting, is the ability to use existing Integrations through integration manager. There are many articles that contain information on how to update the integration so that AA does not interfere, however, until recently, I have not been able to accomplish this.

One difference is that the integration manager node needs to be the eConnect destination – not the standard destination. You will see that the fields are available for the Transaction Dimension, Transaction Dimension Code, and Dimension Code Amount. When mapping to these fields, however, errors are often encountered.

I was able to narrow down one of the causes of the error message I received. It had to do with the Journal Entry field being set to Use Default. eConnect requires a value to be supplied for the journal entry.

In order to resolve, there are two options. Note the next Journal entry number and populate the data within the source file of the integration, and change the Rule for the Journal Entry Number to Use the Source File. The other option is to add a couple scripts to the Integration. One script will be added to the Before Document event script within the Integration manager properties. The other is to set the field to retrieve that number.

Please find the scripts below – Now you can finally take advantage of uploading Journal Entries with Analytical Accounting Information!

Before Integration Script:

Const adCmdStoredProc = 4
Const adParamInput = 1
Const adParamOutput = 2
Const adParamInputOutput = 3
Const adInteger = 3
Const adVarchar = 200
Const adBoolean = 11
Const adChar = 129
Const adDate = 7
Const adNumeric = 131


Dim SqlStmt
Dim objConnection, objCommand, NextJournal


Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")



objConnection.Open _
   "Provider= SQLOLEDB;Server=MGB001\GP11;Database=TWO; Trusted_Connection=yes;"



With objCommand
.ActiveConnection = objConnection
.CommandType = adCmdStoredProc
.CommandText = "glGetNextJEWrapper" 'our wrapper stored proc

.Parameters.Append .CreateParameter ("@IO_iOUTJournalEntry", adInteger, adParamOutput, 4)
.Parameters.Append .CreateParameter ("@O_iErrorState", adInteger, adParamOutput, 4)

.Execute
NextJournal = objCommand.Parameters("@IO_iOUTJournalEntry").Value
End With

SetVariable "gblJounal", NextJournal

Set objCommand = Nothing
Set objConnection = Nothing



Journal Entry field Script:
CurrentField.Value = GetVariable("gblJournal")

 

This article was written by Kaydee Baker, Practice Manager for Tridea Partners. Tridea is a leading Microsoft Dynamics provider.