I found a question in the Dynamics Forum about this subject and answered Mariano Gomez, Mariano detailed all the steps required to fix this up, follow Mariano steps in this article if you found an issue about this subject.
Friday, December 17, 2010
Have you ever restored a database from your backup and wanted an easy way to get users automatically created? script below will do this task for you:
DECLARE @USER varchar(500)
DECLARE @SID varchar(500)
DECLARE CURR CURSOR FOR
SELECT NAME, SID FROM sysusers WHERE issqluser = 1 and (sid is not null and sid <> 0x0)
and suser_sname(sid) is null ORDER BY name
FETCH NEXT FROM CURR INTO @USER, @SID
WHILE @@FETCH_STATUS = 0
EXEC sp_change_users_login 'Auto_Fix', @USER, @SID , @SID
FETCH NEXT FROM CURR INTO @USER, @SID
Above script will read all database level defined users and locate it corresponding users in SQL, if it found the script will map existing user to SQL user, otherwise it will add a new user with a new password and map both users.
Next step required is to change the user password at the application level “Dynamics GP” so it encrypts the user password again and fulfill business requirements.
If you have updated to GP 10.0 SP 5 or GP 2010 SP1 you might already notice the slow performance during login, this is mainly related to the newly added “Dynamics Online Services” dictionary that adds records in the menu table with removing old ones as detailed in this article for David Musgrave and this article for Vaidy Mohan, the temporary solution for this is deleting the records in the menu table that's related to this dictionary.
To avoid the manual deletion of the records in this table, you will need to create an SQL job that automatically deletes unwanted records from this table, follow steps below to start:
1. Open SQL Server, navigate to SQL Server Agent >> Jobs, right click and select “New Job”:
2. Name this Job and click on “Steps”:
3. On steps click on “New”, select your company and paste the following command then click on OK:
DELETE FROM DYNAMICS.dbo.SY07110 WHERE CmdParentDictID = 6499
4. On the new job screen click on schedules and schedule the task to run daily:
5. That’s it, you are ready to go, right click the job and select “Start Job”
Make sure that the job was successfully executed:
Friday, December 10, 2010
I would like to invite you to the biggest IT event by Microsoft this year – the Amman Open Door, December 15-16 at Sheraton Hotel.
Register and attend, we’ll have fun! You can find me in “ASK THE EXPERTS” booth all the time.
Please feel free to share this event.
Monday, December 6, 2010
Its all about extracting data from Dynamics GP! Take a look into Mariano article here and you will understand!
Friday, December 3, 2010
Have you ever wanted to apply your vendors transactions automatically without having to move between all your vendors? I been in a situation with a new client that works on Dynamics GP since 2001 and they never applied their vendors payments to their invoices.
Working on this manually is a real nightmare and the user will keep working on this for ever before being able to finalize, therefore I have wrote script below that generates Macro to set this up, follow steps below to get the macro:
1. Open SQL Server and create new query.
2. Select your company database.
3. Paste code below ** “at the article footer under the signature” and run.
4. Script will generate a macro:
5. Copy macro text and paste it into a new notepad document.
6. Save it under “.Mac” extension.
7. Go to “Transactions >> Purchasing >> Apply Payables Documents”.
8. Go to “Tools >> Macro >> Play” and select the file you just saved:
Enjoy watching your transactions during the apply process.
** SQL Code:
/** SQL Code: **//** By Mohammad R. Daoud **//** Dynamics GP MVP **//** www.mohdaoud.com **//** +962 79 999 65 85 **//** 02-12-2010 **/SELECT VENDORID, CASE WHEN DOCTYPE = 4 THEN 1 WHEN DOCTYPE = 5 THEN 2 WHEN DOCTYPE = 6 THEN 3 END AS DOCTYPE, CASE WHEN DOCTYPE = 4 THEN 'RETURN' WHEN DOCTYPE = 5 THEN 'CREDIT MEMO' WHEN DOCTYPE = 6 THEN 'PAYMENT' END AS DOCTYPEDESC, DOCNUMBR FROM PM20000 WHERE DOCTYPE IN (4,5,6) AND YEAR(DOCDATE) BETWEEN 2001 AND 2017 ORDER BY DOCTYPE, DOCDATE ASCOPEN PMAPPLYWHILE @@FETCH_STATUS = 0Print '##################################'Print 'CheckActiveWin dictionary ''default'' form ''PM_Apply_To_Maintenance'' window ''PM_Apply_Document'''Print 'NewActiveWin dictionary ''default'' form ''PM_Apply_To_Maintenance'' window ''PM_Apply_Document'''Print 'MoveTo field ''Vendor ID'''Print 'TypeTo field ''Vendor ID'' , ''' + LTRIM(RTRIM(@VENDORID)) + ''''Print 'MoveTo field ''Document Number'''Print 'MoveTo field ''Document Type'' item ''' + @DOCTYPE + ''' # ''' + @DOCTYPEDESC + ''''Print 'ClickHit field ''Document Type'' item ' + @DOCTYPE + ' # ''' + @DOCTYPEDESC + ''''Print 'MoveTo field ''Document Number'''Print 'TypeTo field ''Document Number'' , ''' + LTRIM(RTRIM(@DOCNUMBR)) + ''''Print 'MoveTo field ''Auto Apply Button'''Print 'ClickHit field ''Auto Apply Button'''CLOSE PMAPPLYDEALLOCATE PMAPPLY
Thursday, December 2, 2010
David just announced the availability of the support debugging tool build 14, I am not gonna say anything about it and leave you with this article from David @ Developing for Dynamics GP blog.