Probably because those services internally are not as generic as they
should be...
BTW, there is already a place for a phone number extension, is on the
PartyContactMech entity.
-David
On Oct 4, 2006, at 1:34 PM, Amit Shinde wrote:
Hello,
I am using extend-entity ability to add more fields to an existing
OFBiz
entity. These fields are not relational. I am trying to extend
TelecomNumber
table and add a field 'extn' to it. This field represents the Phone
Extension Number. This field is created in the table but no data is
persisted. We call 'createPartyTelecomNumber' service of OFBiz
which in turn
calls 'createTelecomNumber'. Both these service take auto-
attributes of the
TelecomNumber entity for input mode. So, inspite of passing the 'extn'
parameter, it is still not persisted. I cant figure out on what the
reason
is. Any insight will be appreciated.
<extend-entity entity-name="TelecomNumber">
<field name="extnNumber" type="short-varchar"></field>
</extend-entity>
<service name="createTelecomNumber" engine="simple"
location="org/ofbiz/party/contact/ContactMechServices.xml"
invoke="createTelecomNumber" auth="true">
<description>Create a Telecommunications Number</description>
<auto-attributes entity-name="TelecomNumber" include="all"
mode="IN"
optional="true"/>
<attribute name="contactMechId" type="String" mode="OUT"
optional="false"/>
</service>
<service name="createPartyTelecomNumber" engine="simple"
location="org/ofbiz/party/contact/
PartyContactMechServices.xml"
invoke="createPartyTelecomNumber" auth="true">
<description>Create a Telecommunications Number</description>
<auto-attributes entity-name="PartyContactMech" include="all"
mode="IN" optional="true"/>
<auto-attributes entity-name="TelecomNumber" include="nonpk"
mode="IN" optional="true"/>
<attribute name="contactMechPurposeTypeId" type="String"
mode="IN"
optional="true"/>
<attribute name="contactMechId" type="String" mode="OUT"
optional="false"/>
</service>
Thanks in advance,
Amit Shinde
