If I had hair I would be pulling it out right now.
I have been trying to create SSCC labels however I continuously run into problems regarding barcode creation. I have tried both barcode components (in the report designer and just using the component on a page). Neither component appears to be able to correctly encode my data.
In the report writer I am able to get close by using the character ñ to represent the FNC1 escape character to indicate it is a GS1 barcode, this works in report designer, sort of. The value ñ021234567765432137105 seems to validate exactly as I would expect. However, if I try to escape a variable length field such as ñ021234567765432137105ñ15250101 it says "invalid data".
When I attempt to create a barcode using the perspective component on a page. I cannot get it to generate a barcode using GS1-128, the error states invalid barcode value for gs1-128 format, regardless of what I enter as the value. I am probably just missing something really simple here but it would be really helpful is someone could write a short example of how to get the data 02123456776543213710515250101 onto a GS1-128 barcode using either barcode component. When validated the data should read as GS1-128 (02)12345677654321(37)105(15)250101
(01)99327111031766(3102)023450(11)250101(21)87654321
This works as a GS1-128 barcode in the perspective value prop.
Pay special attention to the number of characters in the specification of the zones of the barcode, the 01 section takes 14, so if you use 13 or 15 characters it is invalid.
Thankyou,
I was aware of the GS1 requirements, just unsure on how the data needed to be entered into the value field in designer. The report designer component and the page component function quite differently. I am still unable to generate a valid barcode in report designer, however the page component seems to be operating correctly. FWIW the reason I used the example that I did, is because that is the format we use on our labels. 37 requires an FNC1 to define the end of the variable which doesn't appear to work in Report Designer (again, I might just be missing something here).
Thankyou again, it always helps to see a working example.
(01)99327111031766(3102)023450(37)105(11)250101(21)87654321(37)105
This version successfully renders in perspective, even with 2x 37 identifiers.
Where in the reports do you have the option for a GS1-128?
There is no option specifically for GS1-128. It has been said in other posts that you can insert FUNC1 using the Character ñ to create a GS1-128 compatible barcode using the Code 128 library. Which does work for the most part. The only time I seem to run into an issue with this particular method, is when I use an ñ to end the (37) section and try to add a (15) after. I would think the value ñ021931042100123337105ñ15260114 should work but it doesn't appear to be valid. Interestingly, ñ021931042100123337105, works. As does, ñ0219310421001233ñ15260114 both return a barcode that reads as GS1-128 compatible (although technically 02 requires 37 to be valid according to the standard so this is clearly just a hack way of doing it). I am guessing report designer uses a different library entirely to generate barcodes.
I saw some comments elsewhere indicating that if you use the (37) as the last section, the extra character is not required. Something to do with it not needing to see the end of a dynamic length field.