BAQ Report Bar Codes

Hi All,

created a BAQ report which functions as it should and does exactly what we need it to do…

i now need to add a barcode to reduce some human errors happening in our process.

to add the barcode i have created a new field in the BAQ that adds the * before and after the JobNum field, however the barcodes do not scan - using standard epicor DWBar39 font found in the client folder.

if i try and add the asterix before and after the field manually i get an error. not sure what else i can do - there must be a solution!

I’ve never done barcode formatting within a BAQ itself. I always did in the the report .rdl.

Have you tried it there?

Example:
="*" & Format(Fields!Calc_ReqdQty.Value,"##.##") & "*"

Hi David,

tried manually adding the asterix using the code above, not with the format part but i am unsure how i would format it as its for a job number. (MRP captured jobs that have been firmed up are prefixed with an F, manually created jobs do not have the prefix)

I would think you just use whatever your BAQ column value is. The Barcode is just a font to display the value in a different format.

So, I would think:

="*" & Fields!MyBAQColumn.Value & "*"

… should work.

If your resulting value is 12345 or F12345… the barcode font won’t care. It just format’s the value in that font style.

totally agree it SHOULD work haha

i get the following error…

Error calling AddCatalogItem.
ErrorCode: InternalServerError(500)
Content: {
  "error":{
    "code":"1027","message":"The Value expression for the text box 'UD03_JobNum_c' refers directly to the field 'UD03_JobNum_c' without specifying a dataset aggregate.  When the report contains multiple datasets, field references outside of a data region must be contained within aggregate functions which specify a dataset scope. "
  }
}

i have no idea what any of this means though haha

I think this isn’t necessarily an issue with the field… its an issue with WHERE you’re placing the field in the report.

fixed it!!!

combination of problems,

firstly i have not defined to look for the ‘First’ Job number which fixed the aggregate issue. i then had to wrap the jobnum field in a CStr command so my final line of code on the report for this field is as follows:

="*" & CStr(First(Fields!UD03_JobNum_c.Value, "BAQReportResult")) & "*"

2 Likes