Hi,

I wanted to give an update on this error following our investigation within Product Delivery.

This reply is aimed at third-party developers. If you're getting this error and using third party software that links to Sage 50, please refer them to this response. 

I’ve looked at the Sage50 code, and the transaction post routines work fine.  If the link flag is enabled on a header, any splits will have their link flags set and in reverse, any splits which have the link flag set will update the header link flag. 

The SDO test code supplied within the help guide doesn’t use the post routines, all it’s doing is reading a split record, setting the flag, and writing the record back out.  It never uses the transaction post routine, so the header flag will never get set which results in the error in check data.

If you want to set a linked file on an existing split, then the test code / third party software needs to be updated to set the flag on both the split and the connected header.  

If the developer is using TransactionPost to create splits and headers, and the link flag is set on the header or the split, that should be fine, as the Sage50 transaction post routine would set the link on both the written header and splits.

Hope this information helps.

If this has answered your question please click More > Verify Answer.

Regards,

Ian

Hi,

I wanted to give an update on this error following our investigation within Product Delivery.

This reply is aimed at third-party developers. If you're getting this error and using third party software that links to Sage 50, please refer them to this response. 

I’ve looked at the Sage50 code, and the transaction post routines work fine.  If the link flag is enabled on a header, any splits will have their link flags set and in reverse, any splits which have the link flag set will update the header link flag. 

The SDO test code supplied within the help guide doesn’t use the post routines, all it’s doing is reading a split record, setting the flag, and writing the record back out.  It never uses the transaction post routine, so the header flag will never get set which results in the error in check data.

If you want to set a linked file on an existing split, then the test code / third party software needs to be updated to set the flag on both the split and the connected header.  

If the developer is using TransactionPost to create splits and headers, and the link flag is set on the header or the split, that should be fine, as the Sage50 transaction post routine would set the link on both the written header and splits.

Hope this information helps.

If this has answered your question please click More > Verify Answer.

Regards,

Ian

Hello Ian, 

Can you tell us what the field name on the header is then please?

I have looked at the developer help files for V27 and whilst there is a field "HAS_EXTERNAL_LINK" on the split record, there is no such field on the Header.

Thanks

Roy

Hi Roy,

The header has not had the HAS_EXTERNAL_LINK field exposed in SDO. I've asked for this to be exposed as part of the v27.1 release to ensure external links are posted correctly via SDO.

Hope this helps,

Ian

Thanks Ian

Hi Ian 

I have just downloaded V27.1 help file and there is no mention of the field in the header. Has your request for the field to be exposed not been implemented??

Hi Roy,

I've emailed developer support asking them to update the help files with this information. The person I've emailed isn't back till the 6th of January.

I can confirm the work to expose HAS_EXTERNAL_LINK from the header map to SDO has been done and is part of the 27.1 update. 

SDO 27.1 installer can be found under updates (for Sage 50 Accounts) here >> Download centre | My Sage | Sage (UK) Limited

Let me know how you get on with it.

Thanks,
Ian

Hi  Ian

That seems to work fine now. I have added a line to update the header field and the program works again

Thanks for your help

Roy

Pleased to hear it worked Roy. Thanks again for reporting it. 

Ian