Sage 100

Are there any sData experts out there that might have a clue as to what the attached error log indicates? We have a Sage 100 standard client who is implementing Service Pro from MSI. They are currently in a testing phase and started receiving integration errors related to sales orders that they want us to help decipher. I've started a case with Sage, but have a feeling that the one sData guy at Sage may take a while to get back to me! The highlighting in the attached error log was done by MSI.

Good Luck with that Barb. We have a Customer that purchased MSI directly and they are attempting to connect with SAGE. I couldn't find anyone either.

Why aren't you working with MSI tech support? They would be much more invested in this, and they wrote the integration.

Due to this MSI isn't one of our suppored 3rd party vendors.

Jim, MSI won't take the support case? What do they say?

MSI developed the interface using SData but unfortunately no one really knows how it works

Ouch!

I had a feeling this would be the response! As far as MSi being involved, they say they don't have much luck getting Sage's assistance and wanted us to get the ball rolling. I don't think they really know much about sData, but neither do I - ugh! At this point I'm trying to figure out where to go next and thought we'd check here on the off chance someone might know more that us. I just got off a call in which the client said that he was able to enter an order in Service Pro that created the Sage SO successfully, then he tried entering another order in Service Pro for the same customer and the integration bombed out. BUT, when he rebooted his workstation, that second order went through without error. This would happen a few times and then it would error out again. Their IT suggested checking firewall settings, but any other ideas about that strange development? Of course everything seems to be inconsistent.

Can @AlnoorCassim provide any assistance, direction or wisdom to dealing sData related issues? It seems to me that MSI would be interested in a support agreement with an sData guru on this.

I found this definition of error code 88 - invalid/unknown property name. Odd I was just reading about Sdata today.

I noticed that in the error. I think it means either the code generated by MSI is making an incorrect call, or the Sage 100 side doesn't translate correctly. My money is on the first -- hence I think MSI would pay a consultant to fix their coding.