Friday, February 26, 2021

The account number for actindx xxx needs to be recreated

 This is about a fine GP error message you may receive if you run CheckLinks on the Financial > Account Master.

There are several possible reasons for this error, some of which you may have already found via other references.

My problem with this error, which I've not found a link to, stems from the GL00103 and GL00104 tables.  It seems we had some entries in those two tables with account indexes that were not in the account master.

These represent orphaned allocation accounts and can simply be removed.  Doing so cleared the error messages being report in the Account Master Checklinks.

Hope this helps.

Thursday, February 18, 2021

Jet Reports error regarding Repository Connection

 Here's a beauty of a pile of poo I stepped in.  I was trying to update my Jet Services server to the latest version of Jet Reports tools so I could access the Dashboard Builder.

In doing so I uncheck the boxes for Jet Server because, duh!, they were already installed.

WRONG MOVE!

That just uninstalled the Jet Server components.  So bye bye Jet server.

Took a support case for me to realize how big a flip-up this was.  I was trying to access Jet after this goof and, since the Jet Service windows service was no longer present I was focusing on trying to start the Jet Data Manager Server service.

As Jet Support so ably pointed out that service is only used for a "developer" scenario, which I believe is where multiple developers are using Jet at the same time.  Not my cup of tea but, hey!, open a support case.

Meantime I'd try to start the Jet Data Manager Server and received the following:

"The service started and then stopped again.  The reason for this can be that the user <x> has an incorrect repository connection."

Well, truth be told, the reason for this is I'm an idiot!  I had no business trying to start that service.  It should have been disabled and remained that way.

In reality what I needed to do was re-install the Jet Server components and reconfigure things.  After doing that Jet was back up-and-running and I was back in business.

Please be careful and try not to follow my footsteps!

Dynamics GP Smartlist Builder GoTo Payables version

 Been a while hasn't it.

OK first problem to document is when building a Smartlist (Smartlist Builder) in GP for Payables Transactions and wanting to GoTo the Inquiry window (for example) from the Smartlist.

Easy way to do this is base the Smartlist on the Payables Transaction Smartlist.  This provides a Document Status field that will be used as the ASI_Document_Status value in the BuiltIn GoTo.

So the steps again require the use of the Payables Transaction Smartlist as a Table in the Smartlist.  Once that is established and working set up the GoTo as BuiltIn and with Microsoft Dynamics GP as the Product and Payables Transaction as the Smartlist and Go To as Payables Transaction Inquiry add the Document Status, Document Type, Voucher Number and Vendor ID fields as related to the respective Parameter fields.

This will allow the Inquiry window to open regardless of whether the AP transaction is Unposted, Posted or History.


Tuesday, March 3, 2020

"You can't change the site because the item has quantities committed to another document"

One of our purchasers got this today entering lines in a PO in Dynamics GP.  Not one of our more sophisticated users so was unable to get detailed steps on how he got there.

Regardless found nothing online related to this so I thought I'd post our workaround.

As GP would not allow him to save the line or the order, I had him delete the line.  He was then able to save the PO, and re-enter the item he was previously having trouble with.

I should add he was trying to enter the site for an inventory item when this message showed.  The item site combination was completely valid (as re-entry proved.)

Another mystery message in GP.

Wednesday, November 20, 2019

Dexterity change next requires action

Once again doing battle with Dex ranges.

Kept getting the dreaded "error get/change table...a record was already locked" during a loop on a table with a range where clause.  After the change next on the second record in the range I got the error when attempting to read the third record with a subsequent change next in the loop.

The problem was I did nothing with the second record (by design).  Apparently in every change statement the table record must be saved or removed.

When I added a save command for every record in the loop the error went away.

Tuesday, November 19, 2019

Dynamics GP Payables Apply malfunction

We had a payables payment in GP go bad on us.  When it was put in as a Manual Payment some documents were applied.  This was a partial application and amounts were still outstanding.

However some of these applied documents got disconnected and were left behind.  They showed on the Apply Payables Documents window as being selected with the manual payment, but we could not make any further selections.  When we tried GP kicked the following error:

"This invoice already is partially applied to this credit document.  You cannot apply this document until the other apply amount is posted."

hmmmm....

Found some references to the GP apply tables.  Specifically PM10201, the Payment Apply To Work File, and PM20100, the Apply To OPEN OPEN Temporary File.

For some reason these tables have a LOT of junk in them.  I'm not ever sure how to start cleaning them out.

But for purposes of resolving the current problem I found a bad payment referenced in PM10201 for the invoices that were showing as applied.  I deleted those records and removed the related records from PM20100.  When I ran CheckLinks the apply documents moved to history and all appears back to normal.

Some day there will be a reckoning with those two tables.  It's just a mess.

Tuesday, August 27, 2019

Dynamics GP Attachments - 2 strange animals

We have been jumping into document attachment in GP.  Along the way we encountered some odd issues.  Part of this odd-ness comes from the fact that there are actually 2 separate document attachment processes in GP - one for the main GP dictionary and one for the HR dictionary.

As we have been doing most attachments in the HR/PR area I've quickly realized that this one is a bit under-documented.  For example there are plenty of citations to the main dictionary attachment tables, which range from CO00101 to CO00105.  However I can find few references to the HR attachment tables.

By using GP's Table Finder (on any GP window click Tools > Table Finder) you can find all kinds of juicy info about what you are looking at.


Notice that the box in the bottom left portion of the window shows the Tables involved in this window.  Also notice the tables for this window (HR Attachments) are HR tables.  Furthermore the "Product" is indicated to be Human Resources (HR.)  Normally I use the TableList.xls document in the GP SDK to find tables, but these are not listed there.  Oddly these tables are all in the DYNAMICS database.

HR_AttchRef (HRREF003)
HR_AttachMSTR (HRATT001)
HR_AttachStatus (HRSTA002)
HRAttachmentItems

So the Product being HR is a big clue that there are two separate processes.  This is due to the dictionary architecture of GP and the fact that HR is still a separate dictionary.  While I understand this is the easy way to do this I wonder how hard it would have been to stick with just one attachment process in the main dictionary?

This has interesting implications.  For example in GP under Administration > Setup > Company the Document Attach Setup window has some options to select related to attachments.  However these likely only apply to the main dictionary attachments.  We've not seen any of those options apply to attachments in the HR area.

Probably the worst feature of Doc Attach in GP is the removal.  It is virtually impossible to permanently delete a single attachment.  When you delete from the Attach window it moves to the Delete tab.  From there it can only be removed using the Delete Attachment Files, which is different for the main dictionary and HR.  Further that utility only allows removal with a Date cutoff.

So it's likely my next enhancement to GP will be to allow removal of individual attachments.