Im trying to save a script task in the open process of a lookup but when I try to save it the next message appear: An item with the same key has already been added
And i can´t save the process. I already generate all schemas and compile. But i still have the same problem
Hi everyone! I live in a country where electricity and internet frequently go out, and I have a couple of questions about how this might affect my work with the platform:
If I'm generating schemas and the internet or electricity goes out before the process finishes, do I need to repeat the schema generation once I'm back online, or does the disconnection not affect the process?
The same question applies when compiling the instance. If the compilation is interrupted, do I have to start over, or does the process continue unaffected once I reconnect?
Please note that all of such actions are being executed in the database directly on the server and the end user's connection does not affect the execution.
The only action that it might affect is the package installation from the Application Hub. In some cases errors might occur if you get disconnected while installing a package this way.
What you see on UI is only a visual representation of the ongoing action for the user to be able to track when the action is finished. However, current functionality does not allow to reopen the loading window for such actions after they've been closed.
The only problem is that you will not be able to see the result of the action, as is the case when you finish waiting on the same page where the action was run (for example compilation results).
But the action itself does get completed even if you get disconnected.
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 ?
Full generation is needed to build links between
configuration items. Items can be objects and schemas or
links between packages and their dependencies.
Full generation links them.
Compilation, in addition to its main purpose also generates
source files along the /src path which are necessary when
working with no-code elements and allow you to create an
instance between an object and a table in the DB.
Full generation is needed to build links between
configuration items. Items can be objects and schemas or
links between packages and their dependencies.
Full generation links them.
Compilation, in addition to its main purpose also generates
source files along the /src path which are necessary when
working with no-code elements and allow you to create an
instance between an object and a table in the DB.
We trigger Generate source code for all items on our on-premise system. But upon checking "\Pkg\[Our Custom Package]\Schemas" in our local directory some schemas were missing what could be the problem? Most of our source code schemas were not generated.
Please try to perform the following actions in configurations:
1. Update database structure where needed.
2. Generate source code for all items.
3. Compile all items.
4. Flush Redis.
5. Restart the website.
This should help.
In case there appeared errors on the generation or compilation step, please check the logs (usually can be found in C:\Windows\Temp\Creatio\Youre_Site_Name) to find out the reason of such behavior.
.png){kind=avatar}
