Best Of

Just copy the validation from where it currently exist, create something similar in the web service and utilize it before the create/update function in the web service. This, of course, means it will be inefficient since it's having to do the same thing twice but it does what you're asking. You can get around the inefficiency but you have to ask yourself how often it happens and whether it's worth it with a little more programming.

vinceliu666 wrote: »

Tony_NCD wrote: »

Just copy the validation from where it currently exist, create something similar in the web service and utilize it before the create/update function in the web service. This, of course, means it will be inefficient since it's having to do the same thing twice but it does what you're asking. You can get around the inefficiency but you have to ask yourself how often it happens and whether it's worth it with a little more programming.

Thanks for your feedback , My Issue is that if I run record.insert, the record will be inserted. But I just want to validate data only, not insert record. If I run the record.insert , I must delete the record after insert . But the autoasign no for example Sales Order No will be add one.

Another option is to make a Record Variable: Temporary. By using Temp Tables you can do all CRUD operations without committing anything to your Physical table.

Hello midego,
it looks like you have a Textbox called "Textbox175" and "textbox175". I guess that's the problem.

Looks like 'InstanceName' is the default one. If this server instance isn't available anymore I would suggest to recreate it by the Nav setup. Manually recreating should be possible too but is prone to errors and requires quite a lot of plumbing in my opinion. Unless someone else has a better proposal or solution I would recommend to perform a repair by starting the Nav Setup. Select Repair and now it should recreate the Server Instance which was specified during the setup which ofcourse is the default one. Remember to create a solid backup. Good luck!

Maybe this will help: Log the complete response (of the external service) in a blob field or write additional logic that handles http codes <> 200. If everything is Ok you should get a HTTP 200 OK, else you should get another HTTP Status Code.

Hello @AitorEG,

You could use a TryFunction wrapping the code that could raise the problem to avoid the rollback.

Regards.

Hello @AitorEG,

Yes, something like that,

De nada.

Hi,

Any chance you have one of those Bracket Pair Colorizer extensions installed - they cause this sometimes. My "Bracket Pair Colorizer 2" does/did that until I disabled that.

/Wisa