[Web Application] odd data in classifications.xml or customers.xml

Tony, You have in classifications.xml: <data id="Normal" archetype="classification.customerType" name="Normal" /> <data id="Valued" archetype="classification.customerType" name="Valued" /> <data id="Bad" archetype="classification.customerType" name="Bad" /> <data id="Pensioner" archetype="classification.customerType" name="Pensioner" /> <data id="Monthly" archetype="classification.customerType" name="Monthly" /> <data id="Cash Only" archetype="classification.customerType" name="Cash Only" /> Then in customers.xml <data id="Normal" archetype="classification.customerAccountType" name="Normal" /> <data id="Valued" archetype="classification.customerAccountType" name="Valued" /> <data id="Bad" archetype="classification.customerAccountType" name="Bad" /> <data id="Pensioner" archetype="classification.customerAccountType" name="Pensioner" /> <data id="Monthly" archetype="classification.customerAccountType" name="Monthly" /> <data id="Cash Only" archetype="classification.customerAccountType" name="Cash Only" /> <data id="User One" archetype="classification.customerAccountType" name="User One" /> <data id="User Two" archetype="classification.customerAccountType" name="User Two" /> <data id="User Three" archetype="classification.customerAccountType" name="User Three" /> <data id="User Four" archetype="classification.customerAccountType" name="User Four" /> <data id="User Five" archetype="classification.customerAccountType" name="User Five" /> <data id="User Six" archetype="classification.customerAccountType" name="User Six" /> <data id="User Seven" archetype="classification.customerAccountType" name="User Seven" /> <data id="User Eight" archetype="classification.customerAccountType" name="User Eight" /> I'm not sure if you meant to leave in the User One through Eight. Is that correct? Thanks Lee

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: odd data in classifications.xml or customers.xml

Hi Lee, The demo data came from a data migration for the demonstration database of a legacy system we have in Australia. The data represents two separate classifications. One for customerType and one for customerAccountType. In OpenVPMS these classifications are used for different purposes but legacy system had only one. The classification.customerType is used for demographic customer analysis. The classification.customerAccountType is used to define accounting groups which we will use to define discounts, accounting fees, overdue messages etc. (see Administration->Classifications->Customer Account Type). Hope this makes sense :-) Thanks Tony
Syndicate content