Hi John and Tuzo,
While that may work, there are problems with that approach since during
upgrades, that table may be modified, and if there is a view referencing
it, the upgrade may fail. So, its not a recommended approach.
These tables are "protected" because the API enforces various sharing an
Dear john,
If you have access at the backend(server side) you might need to create
view of that trackedentityattributevalue like
create view te_trackedentutyattributevalue as select * from
trackedentityattributevalue;
And hence use view created in your sql
Thanks
On Tue, 11 Sep 2018, 4:54 p.m.
Hello everyone,
I am having an issue creating a SQL view from the DHIS2 using this query.
SELECT DISTINCT public._orgunitstructure.uidlevel4 AS UID4,
public._organisationunitgroupsetstructure.organisationunitname AS name4,
public._orgunitstructure.uidlevel5 AS UID5, public.organisationunit
3 matches
Mail list logo