33
It would be really nice to have the possibility to define a conditional Flowfield similar to already existing conditional table Relations. I think that SQL Server can handle this easily.
Think of table 27 Item and tables 111 Sales Shipment Line and 113 Sales Invoice Line. We have many programming to fill fields from item table and fill those fields during Posting in CU22 and CU80/90 and others to finish the value from item table in tables 111 and 113 and others.
If we would have a condiitonal Flowfield, we could define this in T111/T113 with relation to the master data field in table 27.
e.g.
exists(IF (TYPE=ITEM) THEN Item.Blocked)) (or many similar fields).
Lookup(IF (T111.Type=Item) THEN Item.Item Category where Item."No." = T111.No.)
Lookup (IF (T111.Type=Item) THEN Item.GTIN where Item."No." = T111.No.)
Of Course the relation must exist of the same type of field for every condition as the condiitonal table relation must also result in the same type of field.
That means a FlowField of Type Boolean must only have boolean result in every condition. Decimal, Integer and Code as well.
In Case of missing defined condiiton as for Type=G/L Account the resulting value will not be Nullvalue (as BC/NAV does not support NullValues) but would be FALSE for boolean, empty for Code, and value=0 for integer/deceimal fields.
Easy enough - I would think this possibility would solve many programming needs which are necessary at the Moment and the execution is passed directly to SQL Server which can handle this internally with simple JOINs.
Category: Development
STATUS DETAILS
Declined
Ideas Administrator

Thank you for your feedback. We are not considering the suggestion at this time due to the following reason: it will be next to impossible to make this work in a stable way inside the server. Add to that that it will be impossible to define a SIFT index on such a flowfield

Sincerely, 

Kennie Nybo Pontoppidan 

PM, Microsoft