So you get the above error and a long string of the fields used in the integration when you try to save the map you created.
To Resolve, export all setups from smartconnect.
Uninistall Smartconnect
Reinstall and 'run as admin'.
All will be fine now.
Trust me ;)
I am a Dynamics GP Consultant with over 14 years Implementation Experience. This is my memory. Everything I learn from my everyday interactions with Dynamics will be posted here as my lesson learnt. My contribution to the world!
Monday, 15 August 2016
Thursday, 11 August 2016
Import Segment Descriptions Dynamics GP
Ok so you have this long listing of segment numbers and segment descriptions to update to your financial setup and dont know how to begin.
You can either use the import method suggested by azurecurve or follow the mailmerge method below.
What you need:
1. Spreadsheet data source with columns - segment_number (the segment position in the chart - segment 2 or 3 for example); segment_value (the segment value within the chart so if it is revenue the number may be 4000 for example); and segment_description.
2. Word merge template
3. End result - SQL Statement
The Word mail merge template will use the spreadsheet as the data source for the mail merge. In this scenario we have a single statement:
update gl40200 set dscriptn = '«segment_description»' where sgmtnumb = '«segment_number»' and sgmntid = '«segment_value»'
The resulting merged data could then be saved as a SQL query and run against the relevant company database. Note that it is best practice to validate database updates in a test environment and to have a current database backup in place before running update statements. Given those warnings, here are the first four lines from a set of sample data:
update gl40200 set dscriptn = 'SC Contracted' where sgmtnumb = '2' and sgmntid = '101'
update gl40200 set dscriptn = 'SC I/H Janitorial' where sgmtnumb = '2' and sgmntid = '102'
update gl40200 set dscriptn = 'SC I/H Janitorial Misc' where sgmtnumb = '2' and sgmntid = '103'
update gl40200 set dscriptn = 'SC I/H HVAC Service' where sgmtnumb = '2' and sgmntid = '104'
Wednesday, 20 July 2016
Dynamics GP Workflow Emails not sending anymore
So your workflow emails used to send but suddenly it stopped.
Reason - Windows password saved on the worflow maintenance window is invalid. Now the system will not tell you this.
All you need to do is go to Admin - Setup - System - Worflow and update the password of the account saved there. Send your test mail and you shall receive it now.
Voila!
Reason - Windows password saved on the worflow maintenance window is invalid. Now the system will not tell you this.
All you need to do is go to Admin - Setup - System - Worflow and update the password of the account saved there. Send your test mail and you shall receive it now.
Voila!
Thursday, 14 July 2016
Capture Login Issues
Ok so you run the capture login script and then get the below message.
supplied parameter sid is in use
you then try to remove the sid from the syslogins table but you get some message related to 'adhoc' something is not allowed.
then you try to create the record manually and get 'the server principal already exists'
How to fix run the below and replace name with the name of the record you have the issue with. You should be fine now.
EXEC sp_droplogin 'namehere'
supplied parameter sid is in use
you then try to remove the sid from the syslogins table but you get some message related to 'adhoc' something is not allowed.
then you try to create the record manually and get 'the server principal already exists'
How to fix run the below and replace name with the name of the record you have the issue with. You should be fine now.
EXEC sp_droplogin 'namehere'
Wednesday, 15 June 2016
SmartList Builder Security
All SmartList Builder windows are denied access by default. To use
SmartList Builder, the user must be in a POWERUSER role, or be granted access
to the following windows in a Microsoft Dynamics GP Security Task:
First go to Security Tasks and select the following as seen in
screen below.
Product: Smartlist Builder
Type: Windows
Series: Project
Go To
Set Field
Options (3 windows)
SmartList
Builder
Second change series to System and select the below as per screen:
·
Background
·
Copy List
·
Display SQL
·
Preview
·
Process Queue
·
Resource Lookup
·
Smartlist Builder Progress
·
Smartlist Lookup
·
Table Details
·
Table Finder(2 items)
·
Upgrade Modified SmartLists
Third - Beyond the Window permissions, there are SmartList Builder
Permissions that need to be granted as well. These SmartList Builder
Permissions can be granted in the Microsoft Dynamics GP Security Task as well.
In same security task change Product to SmartList Builder,
Type to SmartList Builder Permissions and Series to SmartList Builder.
·
Create a Go To that opens a Dynamics GP Form
·
Create a Go To that opens a file
·
Create a Go To that opens a website
·
Create a Go To that opens another SmartList
·
Create a Go To that runs a procedure
·
Create SmartLists with SQL Tables
·
Enter Calculated Fields
·
Update SmartList
·
View SmartLists with SQL Tables
Monday, 13 June 2016
Integration manager - Invalid string
Error: The destination could not be initialized due to the following problem input string
This happens when you run IM as admin and GP as admin BUT - your GP company as a default company marked so when you sign in you have to switch the company you signed in to.
To resolve, remove the 'remember this company' mark from your account just by unclicking it on the sign in window.
Then run GP as admin and select the correct company before getting in and then run IM as admin as well.
Voila!!
It worked for me. Hope it works for you!
This happens when you run IM as admin and GP as admin BUT - your GP company as a default company marked so when you sign in you have to switch the company you signed in to.
To resolve, remove the 'remember this company' mark from your account just by unclicking it on the sign in window.
Then run GP as admin and select the correct company before getting in and then run IM as admin as well.
Voila!!
It worked for me. Hope it works for you!
Management Reporter Database in Suspect Mode
So you check SQL and notice your backups stop running.
Only to notice it is because your MR database is in suspect mode. To resolve the issue i would first suggest, removing MR from the database backup plan and complete your GP backups.
Then run the below script to resolve the MR suspect mode issue. Then create your separate plan for MR backups.
Script:
EXEC sp_resetstatus ManagementReporter;
ALTER DATABASE ManagementReporter SET EMERGENCY
DBCC checkdb(ManagementReporter)
ALTER DATABASE ManagementReporter SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (ManagementReporter, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE ManagementReporter SET MULTI_USER
Only to notice it is because your MR database is in suspect mode. To resolve the issue i would first suggest, removing MR from the database backup plan and complete your GP backups.
Then run the below script to resolve the MR suspect mode issue. Then create your separate plan for MR backups.
Script:
EXEC sp_resetstatus ManagementReporter;
ALTER DATABASE ManagementReporter SET EMERGENCY
DBCC checkdb(ManagementReporter)
ALTER DATABASE ManagementReporter SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (ManagementReporter, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE ManagementReporter SET MULTI_USER
Subscribe to:
Posts (Atom)


