xTuple.com xTupleU Blog & News Customer Support

Suggestions for xTuple 5.0 database

I have been using xTuple 5.0 for about a month or so , without any major issues.

But I see the need for additional fields in the following tables.

  1. public.crmacct
    dba field ( Doing Business As) an alternative name for the business
  2. public.cntcteml
    active flag - to inactivate the email. I can use the cntcteml_invalid field but that is inelegant.
  3. public.cntctphone
    active flag, no way to inactivate the phone. You can change the role to a new role called INACTIVE, but you cannot UNDELETE because you lose the previous role.

In our line of business, we dont delete data, we inactivate it, so then it can be activated again.

Thank you
Bob

Bob,

I’ve entered feature requests 34699 (d/b/a) and 34700 (active flags) to track these requests.

Gil

1 Like

Hi Bob,
Thanks for the suggestions, they are always appreciated. I thought I would add some comments.

[1] We need to be careful at xTuple to add fields that are specific requirements of a company (or a subset of companies) otherwise there is a risk of overly-complex screens with many screen elements not used by most organizations. There are a couple of ways we attempt to address specific company requirements. First is the concept of Characteristics. These are easily definable custom fields that can be added to most xTuple objects/documents. Second, xTuple is very easy to customize and it would not be a stretch to add a specific field to any screen via the inbuilt scripting mechanism. I have done this many times for different companies.

[2] I sort of agree with you regarding the Contact emails. The difficulty there was the way these screens worked. However the current concept behind emails works by assuming the email you see in the Contact form (and is stored in cntct_email) is the active email address. The other emails (stored in cntcteml table) are considered historic or inactive emails - you only want to email a Contact at one address. There is no UI element to control the cntcteml_invalid database column so feel free to script a solution around that.

[3] Contact Phones. Again the UI aspect made it difficult to have active flags in this area. We discussed how to inactivate a phone number without deleting it and our solution was the same as yours - set up an INACTIVE CRM Role. Note changes to Contacts are recorded in Comments so you can trace history as well.

Hope this helps.

1 Like

Thank you for your information. I understand your position on the UI and the trade offs that you have to make.

What I will do is create extension tables to the cntcteml and cntctphone tables in our custom schema with the PK and the active flag. Should do the trick.

Thank you

We ran into an issue with inactive contact phone numbers today. We are still running 5.1. Did the inactive flag get added to the cntcteml and cntctphone tables in 6.0?