You are not logged in.
Dear users of this forum,
we are pleased to inform you that we will be updating the software behind this forum in the near future.
Existing posts, users and categories will remain untouched.
Important:
We will keep you informed in the pinned thread.
Kind regards,
Your ReportServer Team
Liebe Nutzer dieses Forums,
wir freuen uns, euch mitteilen zu können, dass wir in naher Zukunft die Software hinter diesem Forum aktualisieren werden.
Existierende Beiträge, Nutzer und Kategorien bleiben weiterhin bestehen!
Wichtig:
Wir halten euch im angepinnten Beitrag auf dem Laufenden!
Mit vielen Grüßen
Euer ReportServer Team
Pages: 1
Hi All,
Is it possible that the metadata datasource doesn't work in 3.0.8?
I've set everything according to the documentation (https://reportserver.net/en/guides/admi … amic-List/):
1. DB datasource for the ref-table
2. ref-table with the columns: column_name, default_alias, description
3. at the dyn-list definition into the metadata datasource field i selected the datasource for the ref-table
4. the report query return the expected columns
5. the metadata query is simple "SELECT column_name, default_alias, description FROM pte_metadata". pte_metadata is my ref-table, contains the names of the result columns (in column_name), aliases (in default_alias) and descriptions (in description) in each row for each column of the result of the query.
And when I run the query, no aliases, no descriptions.
Did I missed something? I've an 3.0.6 instance of ReportServer, with the same (?) config, which works.
thanks
Tibor
Offline
Hi Tibor,
can you please share some screenshots showing the behavior? You can use http://imgbb.com for posting the images.
Regards,
Eduardo
Offline
Hi Eduardo,
Thank you for your quick answer.
Here are the screenshots:
https://ibb.co/w0MdxCn
https://ibb.co/9rPLKQH
https://ibb.co/K61NTrh
Of course i tried the metadata query with specifying the fields (select column_name, default_alias, description ...).
The RS is Community Edition, RS3.0.8-6009, the DB is GreenPlum (a PostgreSQL fork), but i tried with PostgreSQL 10 too.
thanks
Tibor
Offline
Hi Eduardo,
Solved!
The problem was at the DB side. I put the metadata db to another server, just worked.
Regards
Tibor
Offline
Pages: 1