Solved

Views creation Generation order and priority

  • 22 April 2021
  • 2 replies
  • 24 views

Badge +1

Hi, 

I've defined a view vw_tour_resource. 

Some columns of this view I would reuse in another view vw_tour_driver.

When testing the query itself for the view vw_tour_driver, then in works fine. 

But when creating a new version, then I get an error 

I think the root cause of this is that the view vw_tour_driver is created first before the (existing) view vw_tour_resource as it is alphabetically earlier.

I tried to influence it with Generation order no and Priority, but that seems not working. Tried with giving higher or lower priority, higher or lower Generation order no, but that seems not helping.

How to fix this issue? 

 

icon

Best answer by Mark Jongeling 22 April 2021, 09:42

Hi HJ,

The Generation order no is the order in which code is generated. In this case you have changed the Generation order no of the Functionality. That will not give you the desired result as changing this value only changes its generation position in the Generate definitions screen. 

However, in Data model → Tables you can change the Generation order no of the view and that will result in the view being created earlier or later than others. Having the vw_tour_resource on order no 100 and vw_tour_driver on order no 105 will do the trick. 

View original

2 replies

Userlevel 6
Badge +17

Hi HJ,

The Generation order no is the order in which code is generated. In this case you have changed the Generation order no of the Functionality. That will not give you the desired result as changing this value only changes its generation position in the Generate definitions screen. 

However, in Data model → Tables you can change the Generation order no of the view and that will result in the view being created earlier or later than others. Having the vw_tour_resource on order no 100 and vw_tour_driver on order no 105 will do the trick. 

Badge +1

Thanks for the quick reply!

Reply