When dashboards are added to an edit page, the corresponding records are created in SysWidgetDashboard and SysWidgetDashboardLcz tables.
If a dashboard is added not to an edit page but to the "Dashboards" tab, then records will be added in the SysDashboard and SysDashboardLcz tables, respectively.
.
Also, there is also a corresponding binding of these data to the package which was set as a current package when the dashboards were created.
The thing is that dashboards are localizable system objects. When a dashboard is created, records are created in two tables:
- a record about a dashboard created in the localization, which corresponds to the base culture of the system, is created in the [SysWidgetDashboard]/[SysDashboard] table;
-records about dashboards of all other localizations are created in the [SysWidgetDashboardLcz]/[SysDashboardLcz] table and are linked to a record in the [SysWidgetDashboard]/[SysDashboard] table by the [RecordId] column.
So basically, all you need to do is to prepare a package which will contain all the needed data bindings and SQL scenarios which will perform the records' entry to the tables mentioned above.
More information on data binding is on our academy.
Also, knowledge of SQL might be needed in order to find the needed dashboard in the database, although you can always create a lookup and search via UI.
What schema types CANNOT be configured using the third-party editors in the file system development mode? (Client schemas, Object schemas , schemas with a source code , process schemas)
Can someone explain to me please which can not be configured and why !
If you think of it this way, which schemas are "text" that are easily understood by any 3rd party text editor? Client schemas are Javascript and source code schemas are C#. Both easily understood and editable by a text editor and can be edited by a 3rd party editor. However, object schemas in Creatio use a UI to add columns etc, it isn't just text. Also processes in Creatio have a complete UI process designer, it is not just text. Both objects and processes cannot be edited by a 3rd party editor since it wouldn't understand all the rest of the stuff the designer UIs in Creatio do.
As for the section wizard, this whole detail was created with code, so it would be not possible to enable it. But the first option by clicking the cross sign would be the more simple one.
As for the section wizard, this whole detail was created with code, so it would be not possible to enable it. But the first option by clicking the cross sign would be the more simple one.
Is it possible to export an existing database schema into a creatio datamodel? Or from an ERD Data export?
I use lucidchart to create a model of my database, it has export functions for MySQL, PostgreSQL, SQL Server, Oracle SQL and a similar platform as creatio, Quickbase.
I have an editable list and there are some validations. Due to usability issue, we want it back to the normal detail form with a card schema. The records to the detail are added via multiselect lookup. Is there a way to convert this detail to a normal detail while having source as a multi select lookup?
We have sometimes issues with schema generation and/or compilation.
When we update the system (for example 8.0.0 to 8.0.1) , we can easily find the logs related to generating schemas in the update logs.
But when in "normal conditions", which logs (log names) both in the web app and in the logs folders on Windows should we looking at (to follow progress, to identify any issues) when:
1. Generating schemas
2. Compiling
Any other way to (console debug) to troubleshoot these 2 scenarios ?
All needed application logs for shema generation and compilation can be found in the folder C:\Windows\Temp\Creatio folder. You need to restore the logs and make the following query for your list:
PostgreSQL: Select * from "tablename" where "Logger"='Build' order by "Date" desc limit 200
MSSQL: Select top 200 * from "tablename" (nolock) where Logger"='Build' order by "Date" desc
Yes we know we can find all the application logs in that folder.
There are multiple different logs. Concerning schema generation and compilation, we have find a couple different ones showing up in the past, not always all of them, which sometimes show up after quite a while of generating, and it's hard to say if we need to let the system running or if the system is just stuck...
Please let me reiterate the question: ..... Could you share two full list of of possible application logs file names [for all 3 DBs : MSSQL, PostgreSQL & Oracle] pertaining to:
1. Schema Generation (for example if you just click on "Generate all schemas") and
2. Compilation (if you click on "Compile all")
Thank you for the SQL scripts:
1) Can you share the script for Oracle ?
(yes, their is a 3rd database that you support.. and if not possible to do it with Oracle, indicate specifically that there no script possible. We never know if it is not possible with Oracle, if you forget to provide the information, the latter happens more often)
2) I can be mistaken here: doesn't the table the "build" only show "compilation" information, not schema generation ? For example, if we only do a schema generation (no compilation), will we find information there ?
Hi again, What setting in the nlog.config should I configure to have detailed errors in the compilation?
I change this one, but not sure is the correct one, so I have not build.log file in the log folder
<logger name="ConfigurationBuild" writeTo="universalAppender" minlevel="Fatal" final="true" />
For a specific page schema, the metadata of the page differs from Dev and Test env. The nr of rows is the same , but the content isnt. Is this supposed to be correct ?
Please be informed that the sole fact of the schemas being a bit different is not a problem, the question is does it cause any actual issues to the performance of the site? Also, please specify if the Test env is a full copy of Dev and if so, was that schema present on the Test env before copying? Also, did you make any changes to the schemas yourself?
Parameter IsLocked mainly affects if you can edit the schema or the package. Only the author of the lock can edit these elements. In the database, this author isn't mentioned and you can see only IsLocked.
The system will check the author on the other level.