E10 10.2.200.13 -- Data Directive with a BAQ condition, Unable to complete join due to different data types

,

Has anyone dealt with the occurrence of utilizing a BAQ condition in a directive in which the join can’t be valid due to the joined fields having different data types? I’m trying to utilize a BAQ in which I am joining “ttPORel” for “PONUM” (INT) to “ERP.TranGLC” for “Key1” (NVarchar50). With the directive BAQ being limited compared to the main BAQ designer. I’m kind of stuck on how to handle this?

image

image

image

Yes. In your join fields, you CAN enter functions. Just put your convert(, fieldname) in the source field and your link will work.

Mark W.

It looks like the conditional BAQ method in a data directive does not allow you to type in the fields you wish to join on unlike the normal BAQ designer. I can only select fields.

You can always use a code block :smiley: (well not ALWAYS… but on prem yeah)

@Chris_Conn I was waiting for that comment LOL

Ahhh, missed the DD part. Sorry Dude…

@Mark_Wonsil No problem. Thanks for helping!

Mark,

Does that mean you can’t join the TranGLC table to the PORel.
If you can how is it done.
Any assistance would be gratefully received.

Mark Betts

Just a thought - but could you save the PONum to a string variable ‘Convert.ToString(ttPoRel.PONum)’
and then reference the variable in the criteria for TranGLC, rather than using a join.

1 Like