Juan Sancho-Tello Ripoll asked 2 months ago
Hello,
I don't know exactly when, but from a given moment, when I create new functions, the Assigned Numbers for Table and Page of the same feature are not the same.
While I guess this is not really an issue, it gives problems later on, when I want to create fields that are lookup of those tables. I select the table in the drop-down, but in the "Filter" section it shows me the fields of the list with the same number, but of another table, which leads to errors in the deployment. I try to explain it better here: I have the feature PChar_Helper, Table: 60730, Page 60740
With the fields:
I have another feature PChar_Ing_RR, Table 60720, Page 60730
With the fields:
When I want to add a field that is a Lookup of the feature PChar_Helper I can select it and it shows the number 60730:
But once selected, the fields available for filtering, are the ones of the feature PChar_Ing_RR:
This produces errors when I try to deploy my app with this field.
Could you take a look please?
Thanks!
While I guess this is not really an issue, it gives problems later on, when I want to create fields that are lookup of those tables. I select the table in the drop-down, but in the "Filter" section it shows me the fields of the list with the same number, but of another table, which leads to errors in the deployment. I try to explain it better here: I have the feature PChar_Helper, Table: 60730, Page 60740
With the fields:
I have another feature PChar_Ing_RR, Table 60720, Page 60730
With the fields:
When I want to add a field that is a Lookup of the feature PChar_Helper I can select it and it shows the number 60730:
But once selected, the fields available for filtering, are the ones of the feature PChar_Ing_RR:
This produces errors when I try to deploy my app with this field.
Could you take a look please?
Thanks!
hougaard