Mark, thanks for the help!
Hi Mark, For my understanding… Doesn't the table from your example need a primary key and a column to store the name of the base table?In the end the tenant specific fields should be shown only for specific base tables.For instance: I only want to show the emergency_number field in the customer table. And not in the purchase_order table? I also then have to join the base table and the flexible field table from your example in a view? And have the view presented in a form? Kind regards, Charif
Hi Mark, Thanks for your reply!When using the pivot solution: what type should the free-columns be? This probably has to be a varchar type to keep flexibility? So you have to create extra logic to check the input that is given by the user? For instance should we store date information in the varchar field? I've also been thiking that the most simple solution is to create extra tenant specific columns in the base tables when needed and provide them with a prefix of the tenant. These extra fields should standard be hidden and not mandatory in the datamodel. They should only be made visible in the user interface for the specific tenant. The translation will also not interfere because every field will be unique.When a tenant wants to store extra information in the base table this can also be discussed with the other tenants. If it's usefull for all them then we create a column that is visible by all of them. If it's only needed by 1 tenant than we create the column with the tenant prefix.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
