Table IO Mappings -Very unfriendly behaviour in 8.96F1

[JDEAT]

When designing table IO's like Update, Insert, FetchNext in NER's, FDA or RDA i noticed a very unfriendly behaviour:

Imaging a FetchNext on F4101Z1. There are quite a lot of fields to map.
The problem is, every time I map a variable to the according field in the the table, the tree on the left side of the mapping form is collapsing and i have to open the tree again and have to find the next variable to assign.

This is very time consuming *mmmpffff

I can remember that this happend in previous tools releases as well, but only when the data type of the mapped table field has changed eg from String to MathNumeric.
(See attached JPG)


I noticed this behaviour on E8.10/TR 8.96.F1

Are there any tipps and tricks ?

Regards

 

[Zoltan_Gyimesi]

Hi Andreas,

This behaviour is very old - I know it since B7321.

Check this thread on the Downloads board of JDEList:

Design tools power tool


...and search the latest release in the thread. I hope, it will work on your release and tool set level - and you will find it helpful. In this case thank it to Sebastian Leclerc.

Regards,

Zoltán