Nav 5 Jobs Bug Missing Job No. in G/L Entries

PureHeart

Hi all,

Because of a bug in Nav 5, all the Purchase Invoices (and not only this type of document) posted with a Job No. on the lines haven't got the Job No. field populated in the G/L Entries (in the case of a G/l account type line).
So the problem is that after correcting the bug, i would like now to fix with the correct value the "Job No." in the "G/L Entries".
This is becoming hard because of the grouping in the G/L entries....
Have someone got an idea how to understand which job to link to which g/l entry without having to generate all the possible combinations??

THANKS
Please someone help!!!

PureHeart

nobody had this problem before???
Or nobody knows the answer?
Help aiuto please please!

ara3n

Here is the knowledge base issue on this.

https://mbs.microsoft.com/knowledgebase ... -us;945504


There is no info on how to fix existing data.

ara3n

Maybe contact MS directly and see if they have an internal fix?

PureHeart

Thanks for the Answer!
Yes i did that fix by myself but now i wanted to fix the previous data also!
Microsoft.........................always bugs
And they don't even care about their clients....

ara3n

Sure they care.
Everybody creates bugs.
It's how the industry is built. Client want a solution now asap and they accept some bugs and they support this trend with their money.


If you want bug free software, you would have to pay 10 to 20 more for the software.

Also the tools are not there for automated testing in Navision.

PureHeart

Yes of course noone is immune to bugs....but this one is absolutely stupid....
They have removed a line of code in the C80 and C90....a line that makes the difference...that was a functionality that was working good in the previous version. That's why if you make a bug of this type, putting a bug where everything was working fine, you should even give the client a fix for previous entries.
But this is my point of view, because this is how I operate.
Anyway thanks for your help.
:bug:

ara3n

You are welcome.

Yes deleting code isn't a good thing. I don't delete any standard code.

There has been worse bugs that I've seen. Item tracking/reservation bugs gave me nightmares sometimes.

DenSter

Those were features Rashed

PureHeart

DenSter wrote:

Those were features Rashed

Yes I DO agree....
Anyway if someone is interested, fixing the G/L entries filling them with the right Job No. could be quite complex...
This problem reconduce to the "Subset sum problem", because having an amount for a G/L entry without a Job No. we have to combine the various amounts of the Job Ledger Entries for the Document No. we are consireding. This can be even more complicated in the case we have multiple possible combination and we have to find out which one is the right one.....still thinking of it....but i can't see an easier solution....ideas??

einsTeIn.NET

Hi PureHeart,

could you explain a little bit more in detail what you did to fix the historical data? Or maybe someone else could do?
I'm afraid we are facing with the same problem but didn't notice it until now.