• aRTx
  • Member
  • Offline
  • From: Albania
  • Registered: 10/29/2014
  • Posts: 47

Topic: How to add some info fields for Customer and Supplier!?

In our country when you make an invoce, then if cilent is ABC you must print on invoice these info:
Business Number
Fiscal Number
Tax VAT Number.

How to create FIELDS for all of these info?

Please !!!

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,089

Re: How to add some info fields for Customer and Supplier!?

Customise reports in reporting/repXXX.php and place in your company path - hard code anything you need if it is constant.

apmuthu's Website

  • tm
  • Senior Member
  • Offline
  • From: Sweden
  • Registered: 05/13/2013
  • Posts: 142

Re: How to add some info fields for Customer and Supplier!?

The first thing to check is if there are any fields you're not using. If there is a longer field (like "notes" or something), you might be able to shove all the numbers into that and parse them out when the report/invoice is created.

If that doesn't work, you need to extend the database. This can be done either by adding columns with ALTER TABLE or by creating a new table and linking it to the customer table.

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,089

Re: How to add some info fields for Customer and Supplier!?

@joe: will extending tables with new nullable fields upset any insert/update sqls in FA?

apmuthu's Website

  • joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,085

Re: How to add some info fields for Customer and Supplier!?

It will not be backward compatible. This will have to wait to a major release.

Joe

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,089

Re: How to add some info fields for Customer and Supplier!?

I meant for new installs for endusers. They would not have any backward compatibility issues.

A generic set of attributes in the sysprefs table may be okay for company wide variables but a per table field name / value pair in an attribute table (new) will be okay for now. The following fields:

Table name (without prefix),
Primary_Foreign_Key_Ref,
Attribute_Field_N,
Attribute_Field_N_Value,
Attribute_Value_jsons

An example record in it would be:

items
1
1
Short
{"Color":"blue", "Texture":"Soft"}

apmuthu's Website