Add a "Written" timestamp column when publishing a view to indicate when the data row was modified/written
Have an extra column in the view that indicates when the data row is actually written to the target.
The current timestamp column is the timestamp of the value itself, not when the data row is written.
This will be especially useful for troubleshooting, or when PI Integrator is updating existing value in a target table (will give indication of which data row was recently updated).1 vote
Improve performance of queries resulting in a narrow table. This can happen for queries with many Elements, each with a few Attributes, where bulk queries to the data source are not possible. A narrow table can also result when using * for the Attribute criteria, as each Attribute is then considered a separate match.1 vote
As a PI Integrator Administrator I need to grant permissions to a group of users to configure targets since they are the administrators of the target systems (SQL Server, ADLS, etc.), but they don't need access to other administrator tasks like security management.1 vote
When there are multiple attributes named the same for different elements, the full path is automatically done to avoid duplicated column names. Element without name duplication issue should also have the option to display the full path column name.1 vote
To execute a view with the same parameters, it is actually mandatory to edit the view to be able to execute it again.
It would be nice to be able to force its execution using a right clic on it for example1 vote
When applying a filter when building a shape, the Integrator displays a limited amount of matching elements which is fine.
It would be useful do display the number of element matches as an additional info1 vote
Our end users tend not to have SQL access. We would like to allow them to create clustered indexes to increase the performance of a SQL query on the target view.1 vote
add an option to skip line numbers in the output files1 vote
The output files can grow quite large.
Suggestion :Split the files. Here is an example using AF element name and date :
The AzureSQL Target should not need access to the master database
Current version of PII4BA gives this error message:
Ref the error message
The server principal "sqluser" is not able to access the database
"master" under the current security context.
“Generally, non-administrator accounts do not need access to the master database”
As an integrator for Business Analytics user I would like to be able to choose which directory in Azure data lake my view is published to so that is is easier to manage and analyse data once it is there.
Currently this is only possible through setting up additional targets, which is cumbersome.1 vote
How would this interaction play out? Choose the directory before publishing?
How many directories do you currently need to publish to? What are the different purposes for each directory?
When PI outputs multiple TAGS data to the SQL database, the output table needs only three fields (TAGS, time, value).1 vote
When you add a new attribute to a view, that column is placed at the end of the table. The column should be added in the correct placement like it would be if that attribute was added when the view was first created.1 vote
Currently, it is not possible to set the file extension that is published to Azure Data Lake Store by the PI Integrator for Microsoft Azure. It is currently hardcoded to .txt format.
The end user should have the option to choose which file format (txt /csv/etc) that is to be eventually published to ADLS.1 vote
- Don't see your idea?