I'm building a site which will be integrated in more or less realtime with another internal system. To create and update Umbraco Members I am using a windows service which throws data at the the Members Webservice to create and update them, I think I have to use the WebService as some of the API functionality relies on HttpContext which of course I don't have access to from a windows service.
So, when I come to export Members from Umbraco back into my external system I am trying to load in the members' data in SQL, I'm getting the xml from cmsContentXml and then manipulating it so that I can load each field into a database table.
The problem is this... When I get the cmsContentXml xml it does not contain any generic property data... It seems the xml is only updated after I do a manual save from the Members section. Is this right or am I missing something here? Is there a way to force the cmsContentXml data to update when I first put the member in?
Member Properties not in cmsContentXml until Save
I'm building a site which will be integrated in more or less realtime with another internal system. To create and update Umbraco Members I am using a windows service which throws data at the the Members Webservice to create and update them, I think I have to use the WebService as some of the API functionality relies on HttpContext which of course I don't have access to from a windows service.
So, when I come to export Members from Umbraco back into my external system I am trying to load in the members' data in SQL, I'm getting the xml from cmsContentXml and then manipulating it so that I can load each field into a database table.
The problem is this... When I get the cmsContentXml xml it does not contain any generic property data... It seems the xml is only updated after I do a manual save from the Members section. Is this right or am I missing something here? Is there a way to force the cmsContentXml data to update when I first put the member in?
SQL below:
The answer here was to always ensure that after any kind of member update we always do a member.save() and then the XML is always up-to-date.
is working on a reply...