designer
I have created an end-user reporting application that uses a data
dictionary. When a data-aware component is placed on the designer, the user
is able to view not only the tables and fields defined by the data
dictionary, but all of the pipelines in the whole program. i thought the
purpose of the data dictionary was to control the tables and fields the user
can see... what am i missing here?
dictionary. When a data-aware component is placed on the designer, the user
is able to view not only the tables and fields defined by the data
dictionary, but all of the pipelines in the whole program. i thought the
purpose of the data dictionary was to control the tables and fields the user
can see... what am i missing here?
This discussion has been closed.
Comments
available to the end user when they are visually building a query in the
Data workspace. Set any data pipeline's visibility to false if you do not
want it to be in the list of datapipelines in the report designer Design
workspace.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com