Triggers and table conditionals limitations in Local/Cloud

Fred Thank you, Fred, for your reply. My description is literal and I have tried it in several times: exactly the same triggers work perfectly on cloud and do not work in local; and Createtable if and Deletetable if are simply not available when I am working on cloud (where it is not possible to introduce any code in these fields).

In the attached file, the table 'Sesiones' has this Trigger on create:

let sesion := 'Nr.';
let grupo := Grupos;
let gruposPersonas := (select 'Grupos-Personas' where Grupos = grupo);
for persona in gruposPersonas do
    let nuevaAsistencia := (create Asistencia);
    nuevaAsistencia.(
        'Grupos-Personas' := persona;
        Sesiones := sesion
    )
end

In my Ninox app in MacBook:

• Triggers: If I import the database in a workspace, it works perfectly; if I import the database in local space, it does not work.
• Table conditionals: If I import the database in a workspace, I can not edit Createtable/Deletetable ifs; if I import the database in local space, I can do it and it works perfectly.

I will thank any answer about these limitations.

Claudio

Fred So we have now one answer and still the same other question:

 Createtable if and Deletetable if: These options are available only in Pro subscription. With Standard subscription, I can use these fields in local space, but not in cloud workspaces, because these conditionals have their authentic sense in collaborative workspaces with role-base access permissions (so I can use Createtable if and Deletetable if in local but it is almost not useful to do it).

 What about the trigger on create I mentioned in the attached file (when you add a row in 'Sesiones', some rows are added in 'Asistencia' automatically)? Could you try that, please? If I import the database in a workspace, the trigger works perfectly; if I import the database in local space (out of cloud), it does not work.

Than you so much.

Claudio

Fred Thank you again for all your attention and help. I will use buttons instead of triggers if I need a "trigger" in a local database. But triggers must work too, so I will inform to Ninox as you recommended.

It appears to be different bugs/limitations when working in local. Recently, I have checked that pages do not work properly in local and work perfectly in cloud workspaces (again: using exactly the same database). Some bothers that I will end avoiding by working always on cloud, what is other bother for me in some cases.

I will mark the topic as answered:

 Role-based access permissions are not available in Starter subscription and this also seems to affect to the fields Createtable if and Deletetable if (which are not available in workspaces with a Starter subscription). The fact we can use these fields in local databases (non collaborative space) is like a "present" from Ninox, almost useless precisely out of collaborative cloud.

 Some triggers do not seem to work in local databases; they work only in cloud workspaces. And I will ask Ninox for this bug/restriction and other ones recently detected, like pages working wrong in local databases.

 Provisional solution: Working always in cloud workspaces and accept the limitations of Starter subscription.

Thank you so much. Best regards.

Fred I agree with you. The link is made (the child record is associated with the parent record), but, for some reason, the field seems empty when the trigger tries to get the information