==== Table properties ====
{{ :configuration:tableprop.png?nolink&300|}} If you open a table in LISA you will get a graphical representation, similar to how it will look in Lime CRM. Once the table is opened, __click anywhere in the header on the table__ and you can choose properties for the table to the right. Besides the properties you specified when you created the table, you can also choose for example where in LIME the table should appear ("Table Order") and which actionpad should be the default (the html-area to the left when you open an object for this table in LIME).

You can also add a **descriptive expression**, which is used to specify which information should be printed out when using an object of this table. An empty descriptive expression will return the id number of the object. See example below

==== Descriptive Expressions ====

As described, Descriptive Expressions are SQL code. When typing them, the format is that you write the following

<code>
SELECT --This is predefined and not visible

[company].[name]–this is what you modify

FROM [tablename] WHERE [idTABLENAME]= THE_ID_OF_THE_CURRENT CARD –This is predefined and not visible
</code>

If you need to do a subquery, you should have it within (). An example could be when getting something from the string table, to get the text from an option field. See the example below as well.

<code>
SELECT --This is predefined and not visible

(SELECT [da] FROM [string] WHERE [idstring] = [company].[buyingstatus]) -- this is what you modify

FROM [tablename] WHERE [idTABLENAME] = THE_ID_OF_THE_CURRENT_CARD -- This is predefined and not visible
</code>

In the above example we get the Danish text from the option field Buying Status.

If you need to combine multiple things, you can do it by using the + sign. Just remember that you need to add whitespaces manually.

<code>
[company].[name] + ' - ' + [company].[city]
</code>

The above example simply adds the Company name, then a whitespace a - another whitespace and then the city.

=== Descriptive examples ===

Here you can find code to descriptive expressions that we use often. This code can be a start point that you can modify when creating your own descriptive expressions.

__Company name as descriptive on an other card__

Set company name as descriptive expression on a Role table (not on the company card, if you have an other table just change role to your table name):

<code>
(Select[name]from[company]where[company].[idcompany]=[role].[company])
</code>

__An option from a option list as descriptive__

If you want to have a option from a option list as a dresciptive expression use the following code. This eg. gets the TypeOfRole from a Role table to be used as a descriptive expression. If you want to get an other language change sv to correct language.

<code>
(Select[sv]from[string]where[string].[idstring]=[role].[typeofrole])
</code>

__Two fields as descriptive expression__

If you also want to have the company name and role as a descriptive expression, eg. &quot;Lundalogik - Supplier&quot; (Supplier is a 'typeofrole') use the following code:

<code>
(Select[name]from[company]where[comany].[idcompany]=[role].[company])+' - '+(Select[sv]from[string]where[string].[idstring]=[role].[typeofrole])
</code>

Don't forget the brackets!

==== Table properties ====

^ Name      ^ Description       ^
| ''Invisible'' | Select if a table should be invisible for everyone, just for administrators or for no one.|
| ''Table label'' | Used by the web client. Changes to standard tables can break the web client.|
| ''Default Actionpad'' | This should not be changed unless you're aware of the consequences.|
| ''Descriptive Expression'' | The code in this field, defines the title of the table as shown in the top left part of the card and through relations. If no Descriptive Expression is written, the ID of the card will be shown through relations and as the title on the card.|
| ''Display name'' | Here you can change the language dependent display name that is visible in Lime CRM|
| ''Log all changes'' | Enables the changelog for the table. This can affect performance, and it's suggested only to be turned on for debugging.|
| ''Name'' | The database name of the table. Changing this can break Lime CRM and therefore it should never be changed.|
| ''Private comment'' | The possibility to add a comment that is only visibly through LISA.|
| ''Security policy'' | Which security policy is enabled for this table. Security Policies are used to restrict access to tables and fields. You can read more about Security Policies in the chapter _Security -Policies_.|
| ''Table order'' | The tables order in the overview.|
| ''Record acces properties'' | Advanced object security. Do not add/change anything here unless you are 100% sure you know what you are doing.|
| ''Displayname'' | Here you can change the singular name of the table.|

==== Record Access ====
Please see [[/configuration/record-access|Record access]]