Skip to Content

In the course of performance improvement we made a change in our POWLs that can lead to a small confusing “issue”, some of you might already have or will experience in the future.

To improve performance, only fields that are initially shown in your POWL view will be filled when opening a certain POWL. In other words, fields that are initially hidden and can be added via personalization remain unfilled at that time.

So if we add for example the “Created On” field to our Freight Order POWL by using the personalization button, it will remain empty after adding it in the first place.POWL_refresh1.jpg

Just one click on the refresh button and all POWL fields included the “Created On” will be filled.

POWL_refresh2.jpg

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

    1. Dragos Mihai Florescu

      Hi Rajiv,

      no there aren’t.

      One of the reasons is the fact that it depends on the fields in question. If the optimization happens for a field from a BO node that is read anyway (e.g. an attribute from ROOT, like Created By), then the only improvement is the fact that less data is transported from DB server to application server. But if the field requires a long path (e.g. address details), then the gain could be noticeable.

      Cheers,

      Dragos

      (0) 

Leave a Reply