I am getting the same error.  Our plan is to use AD groups to map to Outsystems Roles and Teams.

This is the SQL Code that has the error:

SyntaxEditor Code Snippet

SELECT TOP 1
    Role.[Name]
FROM {User}
INNER JOIN OSLTM_INFRASTRUCTUREUSER UserRoles   ON UserRoles.[UserId] = {User}.[Id]
INNER JOIN OSLTM_INFRASTRUCTUREROLE Role        ON UserRoles.[RoleId] = Role.[Id]
WHERE
    {User}.[Id] = @UserId 
    AND {User}.[Is_Active] = 1
    AND Role.[Name] <> 'Everyone'

Hi,

Any news on this topic, just installed the plugin in OS11 and get the same errors on this advanced SQL:

As of OS11 LifeTime has ALWAYS its own (lt) environment.

Anyhow the Isolated Lifetime Env if will check this, but I don't understand why the advanced SQL uses as it looks like an internal OS View, that as of version 11 of OutSystems generates an error.

Can I replace the advanced SQL not with calles to the LifeTimeUserManagement api?

Regards,

Daniel

This tool is still not working.  Is there anyone available to look at this tool?

Hi Chip,

I agree with you, I really hope some support is given on this tool by its owner.

Regards,

Daniel

Hi guys,

All these issues should have been fixed with the latest version of this component.

Happy Coding,

João Pêgas.

The new version is working.  Thank you Joao.

-Chip