You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking into the logs, it's comes clear on why this shouldn't be possible.
Invalid column name 'Location Filter'.
Statement(s) could not be prepared.
SQL-instructie:
SELECT TOP (1) "AssemblyLine"."No_" AS "ItemNumber","AssemblyLine"."Location Code" AS "LocationCode","AssemblyLine"."Document Type" AS "AssemblyLine$Document Type","AssemblyLine"."Document No_" AS "AssemblyLine$Document No_","AssemblyLine"."Line No_" AS "AssemblyLine$Line No_",ISNULL("SUB$Item$Inventory"."Inventory$Item Ledger Entry$SUM$Quantity",0.0) AS "Inventory" FROM "default".dbo."CRONUS BE$Assembly Line$437dbf0e-84ff-417a-965d-ed2bb9650972" AS "AssemblyLine" WITH(READUNCOMMITTED) LEFT OUTER JOIN "default".dbo."CRONUS BE$Item$437dbf0e-84ff-417a-965d-ed2bb9650972" AS "Item" WITH(READUNCOMMITTED) ON (ISNULL("Item"."No_",N'')=ISNULL("AssemblyLine"."No_",N'') AND ISNULL("Item"."Location Filter",N'')=ISNULL("AssemblyLine"."Location Code",N'')) OUTER APPLY (SELECT TOP (1) SUM("Inventory$Item Ledger Entry"."SUM$Quantity") AS "Inventory$Item Ledger Entry$SUM$Quantity" FROM "default".dbo."CRONUS BE$Item Ledger Entry$437dbf0e-84ff-417a-965d-ed2bb9650972$VSIFT$Key2" AS "Inventory$Item Ledger Entry" WITH(READUNCOMMITTED,NOEXPAND) WHERE ("Inventory$Item Ledger Entry"."Item No_"=ISNULL("Item"."No_",N''))) AS "SUB$Item$Inventory" WHERE ("AssemblyLine"."Type"=@0) AND (ISNULL("AssemblyLine"."Document Type",0)=@1 AND ISNULL("AssemblyLine"."Document No_",N'')=@2 AND ISNULL("AssemblyLine"."Line No_",0)>=@3 OR ISNULL("AssemblyLine"."Document Type",0)=@1 AND ISNULL("AssemblyLine"."Document No_",N'')>@2 OR ISNULL("AssemblyLine"."Document Type",0)>@1) ORDER BY "AssemblyLine$Document Type" ASC,"AssemblyLine$Document No_" ASC,"AssemblyLine$Line No_" ASC OPTION(FAST 50)
So a new rule on preventing including a Flow Filter field in the DataItemLink property. Probarly there are more cases where we could verify this, maybe also on the DataItemTableFilter property? (not 100% sure, I should test this)
Could use some help here to gather more possible situations which I'm not thinking about right now.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When creating a query object, with a Flow Filter column (Item."Location Filter"), will result in a runtime error on executing the query.
When looking into the logs, it's comes clear on why this shouldn't be possible.
So a new rule on preventing including a Flow Filter field in the DataItemLink property. Probarly there are more cases where we could verify this, maybe also on the DataItemTableFilter property? (not 100% sure, I should test this)
Could use some help here to gather more possible situations which I'm not thinking about right now.
Beta Was this translation helpful? Give feedback.
All reactions