A while back we logged a case with BaaN support regarding an apparent loss of functionality when the Print Return Note report was copied.

Report tdpur441101000 was cloned, some minor cosmetic changes were applied to it, then this cloned report was added as the 3nd report option to session tdpur4411m000. But we found that the customized report wasn't incrementing the order step.

After several weeks, BaaN eventually came back to say that the Print Return Note report will only update the procedure mask if it is report number 1 on the session.

Has anyone encountered other examples of this kind of customization constraint (effectively, you can't have multiple Print Return Note reports)? Are these constraints documented anywhere.

Thanks.

I have not seen where things like this are documented. I have also had the support center tell me one thing, when another is true. So if you have the source code for this I would trace thru the code and find out if this is true. Or hope that someone here with source(or appropriate knowledge) replies to your message. Sorry to say that we do not own the source.

Not that I am knocking the support center, but there have been instances where the user community reports one thing and the support center told me something else.

Good Luck!

Mark

for this session is true, then, you can modify the source to accept report 3:

reportno = 1 -> old
reportno = 1 or report = 3 -> new

with this modifications the program will modify the mask

Sorry David a quick source inspection has revealed that the session does indeed check the 'reportno' variable it must be '1' in order for the procedure mask to be updated to an 'e'. The reason behind doing this is because report number 2 is a simple list it should not update the procedure mask when printed.
Your first option is to link your customized report as report #1, the other option is of course to approach your local support center.

What version of baan are you on, maybe I can help you?


Rupert

Actually these little things make me love Baan...

You cannot fool the system, unless you really understand what you are doing. And this understanding must be both functional as technical. Only then you are able to do it correct.

I really like this.

If you have the source code and want to use the new customized report, then you should change the code as mentioned by bizen.

Thanks for the helpful replies.

Unfortunately, we do not have a developers licence, so it isn't an option to modify the session script as bizen & Morpheus suggest. However, I think I can do what I need to do in the report script by formatting conditional print statements based on the company number: this way, different logistics companies can use the same report and obtain different outputs.

My main concern (and the real reason why I rasied the thread) was to highlight what I feel is a rather surreptitious (almost unfriendly) feature of BaaN tools. Without a developers licence, how would a user know about this conditional updating of the procedure mask? Worse still, when we logged the call with BaaN Support they initially insisted they couldn't reproduce the problem at their end (despite it being, as we know now, standard BaaN functionality!) and the case dragged on for weeks. Perhaps I should have come to the BaanBoard in the first place and got the answer from you guys within an hour!

Thanks again for you assistance.

Hi,

You can try tu put the new report at the same group that the first

I think, because I had not tryed

Good Luck

There is this option to gain sources even when you do not have the developers lisence; see the SP booklet.

In that way you can have the sources after they have been updated.

Luuk,
What is this SP booklet? Do you mean Service Pack installation guide!? From where to get it?

See solution 127360: Documentation belonging to Service Pack 11 for BaanIVc4 (installation guide, release notes etc.) ... and the others are also contained in solutions...