Darron Cockram
Darron Cockram
I'll raise it with the Accounts team but I believe that it's by design that those fields aren't exposed as there is no equivalent in the GCRM contract.
Last I heard there were no plans on exposing these fields to the Sdata feeds I'm afraid.
Not sure why that would be the case as the commodity resource kind does have an updated property and it is returned in the ATOM feed format but I've raised...
It's definitely on the list of issues to be fixed but is with the Accounts team at the moment so I don't have an ETA at the moment I'm afraid....
Afraid not. The only workaround at the moment would be to use the application/atom+xml content type as the updated updated date does appear in that.
I don't think the active flag maps to anything. I'll raise it with the Accounts team.
It's still outstanding I'm afraid. I'll let the Accounts team know the issue has been raised again but unfortunately I have no control over their backlog so cannot say if/when...
The Accounts roadmap is on the main website here https://my.sage.co.uk/public/help.aspx#/roadmap/sage-50-accounts. It's not as detailed as the internal backlog so individual bugs typically won't be visible there but you can submit...
The only workaround would be to use the status field to determine if the status is set to 'closed' or not. Note however that the actual test of the account...
I've replicated the issue and can confirm it's a bug with the Sage 50 Accounts Sdata implementation so I've raised it with the Accounts team.