Doubled up Lookup.local on entity.documenttemplate archetype

So I somehow managed to endup with a double up in the lookup.local for 

entity.documentTemplate.

in the propertymap I have 2 entries for customercredit

The LinKID's for each are different, and if I select my credit report to the wrong entry it wont print.

So...how do I determine the entry to remove....

 

 

I can select the corect entry via trial and error in the webapp but I cant remove it in the webapp.

 

 

{code}
<linkId>cbb73905-b109-11e1-b25a-133c60f4fba2</linkId>
            <name>act.customerAccountChargesCredit</name>
            <version>0</version>
            <details/>
            <type>java.lang.String</type>
            <value>Customer Credit</value>
          </org.openvpms.component.business.domain.im.datatypes.property.AssertionProperty>
          <org.openvpms.component.business.domain.im.datatypes.property.AssertionProperty>
            <id>-1</id>
            <active>true</active>
            <archetypeId>
              <entityName>descriptor</entityName>
              <concept>assertionProperty</concept>
              <version>1.0</version>
              <qualifiedName>descriptor.assertionProperty.1.0</qualifiedName>
              <shortName>descriptor.assertionProperty</shortName>
            </archetypeId>
            <linkId>cbb73906-b109-11e1-b25a-133c60f4fba2</linkId>
.......
......
.....
            <name>act.customerAccountChargesCounter</name>
            5a-133c60f4fba2</linkId>
            <name>act.customerEstimation</name>
            <version>0</version>
            <details/>
            <type>java.lang.String</type>
            <value>Customer Estimation</value>
          </org.openvpms.component.business.domain.im.datatypes.property.AssertionProperty>
          <org.openvpms.component.business.domain.im.datatypes.property.AssertionProperty>
            <id>-1</id>
            <active>true</active>
            <archetypeId>
              <entityName>descriptor</entityName>
              <concept>assertionProperty</concept>
              <version>1.0</version>
              <qualifiedName>descriptor.assertionProperty.1.0</qualifiedName>
              <shortName>descriptor.assertionProperty</shortName>
            </archetypeId>
            <linkId>cbb73908-b109-11e1-b25a-133c60f4fba2</linkId>
            <name>act.customerAccountChargesCredit</name>
            <version>0</version>
            <details/>
            <type>java.lang.String</type>
            <value>Customer Credit</value>
          </org.openvpms.component.business.domain.im.datatypes.property.AssertionProperty>
{code}

Comment viewing options

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

Re: Doubled up Lookup.local on entity.documenttemplate archetype

The entity.documentTemplate archetype is incorrect. It has a duplicate entry from Customer Credit:

     <node displayName="Type" name="archetype" path="/details/archetype" type="java.lang.String" minCardinality="0">
            <assertion name="lookup.local">
                <propertyList name="entries">
                    <property name="act.customerAccountChargesCredit" value="Customer Credit"/>
<!-- SNIP -->
                    <property name="act.customerAccountChargesCounter" value="Customer Counter Sale"/>
                    <property name="act.customerEstimation" value="Customer Estimation"/>
                    <property name="act.customerAccountChargesCredit" value="Customer Credit"/>
<!-- SNIP -->
                </propertyList>
                <errorMessage>errorMessage</errorMessage>
            </assertion>
        </node> 

You can edit the entity.documentTemplate.adl file in:

 $OPENVPMS_HOME/update/archetypes/org/openvpms/archetype/document/entity.documentTemplate.adl 

and remove the second instance. Reloading archetypes will delete it from the database.

That said, I'm not sure its the cause of your problem. Whats the error message?

-Tim

Re: Doubled up Lookup.local on entity.documenttemplate archetype

The error was just the standard "NO template associated with this ...." error

I assumed it was because the print button in the customer account workspace was associated with a specific credit linkid

If I change it to the other Customer Credit report type it works no probs

Ben

Syndicate content