Infolog does not show up

(0) Share

Report

Posted on by Community Member

Hi,

we have a really weird error. All the InventTransOrigin* tables have a writeOriginOwnerRelationship() method. Those methods get the current number of infolog lines by using the infologLine() function. In the catch block there is an infolog.clear() using the number of infolog lines that were saved before to remove all infos created by the method.

Now the problem is, that randomly (I really don't know when - it seems impossible to find a cause for this behaviour) the infologLine() funtion returns 0 altough there are previous infos. This results in the entire infolog being cleared, removing all relevant messages. However when you debug the writeOriginOwnerRelationship() method it work every single time. If you dont debug, it seems to be random. Sometimes I get the infos 10 times and all of sudden they stop appearing (I don`t change the way I`m testing - I keep doing the same thing) and sometimes they don`t appear straight away.

Anyone has an idea what could be the cause for this?

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Sort by

Martin Dráb 239,647 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

It doesn't answer the question, nevertheless note that the problem with infologLine() was also reported in Global::infologLine periodically returning wrong line count after CU7 upgrade.

Was this reply helpful? Yes No
Douglas Noel 3,907 on at

Like (1)

Report
Copy link

Link copied!

Hi Jens, Hi all:

can you have a look at the follwing thread:

community.dynamics.com/.../160905

seems to be the same problem

can you additionally take at a look at the 2012R3 stated issue (LCS)

'Issue 3626411 Return value of infologLine() is sometimes wrong'

Seems to be a known issue, but no fix at the moment. And it isn't occuring on R3 only.

regrads

Douglas

Was this reply helpful? Yes No
Douglas Noel 3,907 on at

Like (0)

Report
Copy link

Link copied!

Hi Jens,

this seems to be an annoying problem. But maybe you can help others. It seems to be that you have the advantage that you can reproduce this in a 'relative' easy way.

Can you please check what happens if you replace the code in the Global class method infologline with a 'return infolog.line() '

ONLY FOR TEST !!!!!

Are the problems still persist?

regards

Douglas

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Douglas,

I replaced the code in the global class and indeed it is working. I also noted that adding 'infolog.reloadRunningMode()' before the call to infologLine() resolves the issue.

Unfortunately both solutions are not really practicable because they create client calls lowering the performance (the writeOriginOwnerRelationship() methods are called very frequently and run on server)

Thanks for your suggestion anyway

Was this reply helpful? Yes No
Douglas Noel 3,907 on at

Like (0)

Report
Copy link

Link copied!

Hi Jens,

thank you for giving us your results. Did you find a difference in this behaviour running server code in CIL / not in CIL ?

Of course - reloadRunningMode() will 'synch' these 'server counter' which was introduces in xglobal class. But I ask myselfe how this should work without a 'inter tier' call.

Maybe MS has had some flaw in the concept here. Keep us watching this.

regards

Douglas

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

I couldn't find any difference in CIL/no CIL. Both work.

The infologLine method works without client calls (also stated in the XML documentation) but as you said, there seem to be some flaws in there...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

We also experiment that issue when we modify purchase line quantity.

We have been put on the way of infologline with that post dynamicsuser.net/.../82830.aspx

Using the deprecated method solve the issue, but...

Was this reply helpful? Yes No
Douglas Noel 3,907 on at

Like (2)

Report
Copy link

Link copied!

Hi Benoit,

I think we have to wait until MS is going to fix this. But it seems to be really interesting what MS currently would suggest as workaraound for this really annoying problem. Maybe using the 'deprecated' infolog.line() call seems to be the best way until this is fixed. This problem has to be fixed - it's really really annoying - you should rely on such basic things.

If think they should take this 'feuture' seriously and release a fix for that - even if the fix will be a modified global::infologline method which calls the deprecated one.

The more people are going to complain about this, the sooner the fix has to be created..

regards

Douglas

Was this reply helpful? Yes No
Douglas Noel 3,907 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

anything new on that topic?

Does somone know if there was released a hotfix for that?

I'm currently still have a reference to an Issue 3626411: 'Return value of infologLine() is sometimes wrong' which has the status postponed.

Is this maybe fixed in some kernel hotfix in the meanwhile (without explicitely declaring this) ? Or is it really still active?

regards

Douglas

Was this reply helpful? Yes No
Puneet Darji 168 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Current status as well is same i.e. postponed. Our client is also suffering badly due to this. Anyone has idea when its going to be fixed or any workaround?

Thanks in advance!

Was this reply helpful? Yes No