Translate Between JSON and EDI
11–15 of 15 posts
Re: Translate Between JSON and EDI
#12EDI is a bitch. X12 is not great. IIRC, and it's been a while, so I may not, it's essentially a positional Character Separated Value stream. You basically build a string and fill in data or nothing as appropriate. For example the result looks something like *START*VALUE1*10.00*BOB*DOLE*100*ADDRESS*STREET* Where the double asterisk is where a blank value is. However, it is a standard. It is knowable. You can get the A…
It's difficult to use the method you're describing to write a transaction like this, particularly when the receiver's system can fall over due to a single character out of place: https://www.verizon.com/business/support/vec/onlinehelp/dam/...
(I'm the CEO of Stedi)
Re: Translate Between JSON and EDI
#13EDI is a bitch. X12 is not great. IIRC, and it's been a while, so I may not, it's essentially a positional Character Separated Value stream. You basically build a string and fill in data or nothing as appropriate. For example the result looks something like *START*VALUE1*10.00*BOB*DOLE*100*ADDRESS*STREET* Where the double asterisk is where a blank value is. However, it is a standard. It is knowable. You can get the A…
It's definitely possible to write simple EDI transactions (no HL loops, etc) with a couple of trading partners using something akin to mustache templates – many of our customers come to us after getting something basic like this up and running in a day or two, and then hitting complexity. It's difficult to use the method you're describing to write a transaction like this, particularly when the receiver's system can f…
So, you know, Healthcare billing information. It's tedious, but the worst part is the mapping from your own data source to the format. And you don't help with that part.
Re: Translate Between JSON and EDI
#14Earlier quoted context omitted.
It's definitely possible to write simple EDI transactions (no HL loops, etc) with a couple of trading partners using something akin to mustache templates – many of our customers come to us after getting something basic like this up and running in a day or two, and then hitting complexity. It's difficult to use the method you're describing to write a transaction like this, particularly when the receiver's system can f…
I had to process ANSI X12 835/837 sending and receiving. So, you know, Healthcare billing information. It's tedious, but the worst part is the mapping from your own data source to the format. And you don't help with that part.
We've found that many of the fields end up being single-item enums, so those can be hardcoded (i.e. no mapping required). Guides (https://www.stedi.com/products/guides) generates JSON Schema for you, and Mappings (https://www.stedi.com/products/mappings) automatically populates any single-item enum. Both are free to configure in the UI.
Re: Translate Between JSON and EDI
#15No option presented for installing locally, must make all calls to their api servers.