Welcome!

This community is for professionals and enthusiasts of the Genio platform.
Share your questions and challenges, and help your partners!

1

1
David G.
On 5/5/20, 5:03 PM

The workaround you made is a valid solution although in terms of scalability it is not the the recommended way. If you're certain that your system will only have one entity you can use the GLOB table that only has one record (always). This is the solution to avoid the creation of a table with only one record. Again, this is a workaround. The recommended solution is to have a table of entities that is related with all the components of your system. This way, your system becomes easily scalable.

  • Flag

I don´t see any GLOB table in the project definitions.

Annabelle Le Rohellec
on 5/5/20, 5:15 PM

When creating a table with a GLOB identifier, Genio considers it special. It is special because it only allows one and only one registration. All fields / attributes placed in this table can be accessed by the other tables, for example for use in calculation formulas.

Each field in the GLOB functions as a global variable to the system. There is no need for relations with the GLOB. As such, it is completely discouraged to have a 1: N relationship with the GLOB.

N: 1 relations with the GLOB are allowed, for example the need to want the value of a primary key of a given table in a given field of the GLOB.

The solution to use GLOB to solve the presented challenge works today, but is not guaranteed to work in the future. Therefore, it is completely discouraged to use GLOB to solve even if the solution works in this particular case.

Álvaro Damas
on 5/6/20, 3:18 PM

Keep Informed

About This Community

This platform is for beginners and experts willing to share their Genio knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers. Read Guidelines

Question tools

20 follower(s)

Stats

Asked: 5/5/20, 11:26 AM
Seen: 168 times
Last updated: 8/22/20, 3:40 PM