<![CDATA[FrontAccounting forum — Field crm_contacts.entity_id should be INT]]> 2014-10-08T19:06:49Z PunBB https://frontaccounting.com/punbb/viewtopic.php?id=5231 <![CDATA[Re: Field crm_contacts.entity_id should be INT]]> It should not cause any problems if we change it in v2.3 itself isn't it?

]]> https://frontaccounting.com/punbb/profile.php?id=364 2014-10-08T19:06:49Z https://frontaccounting.com/punbb/viewtopic.php?pid=21100#p21100 <![CDATA[Re: Field crm_contacts.entity_id should be INT]]> Yes, seems this good candidate for change in 2.4.
Janusz

]]> https://frontaccounting.com/punbb/profile.php?id=89 2014-10-08T19:03:32Z https://frontaccounting.com/punbb/viewtopic.php?pid=21099#p21099 <![CDATA[Field crm_contacts.entity_id should be INT]]> The field crm_contacts.entity_id is used to look up the cust_branch.branch_code in reporting/rep103.php and hence both must be of the same field type. The former is VARCHAR(11) whilst the latter is INT(11). Any reason why the former remains VARCHAR?

The file sales/includes/db/branches_db.inc too uses the entity_id field to lookup the branch_code in a similar way.

]]> https://frontaccounting.com/punbb/profile.php?id=364 2014-10-07T14:50:22Z https://frontaccounting.com/punbb/viewtopic.php?pid=21079#p21079