The ItemID of PI tags retrieved using the PI OPC DA Server has a backslash. In order to maintain consistency with browsing for OPC tags on their client, is there a way to remove or replace the backslash in the ItemID? For example, <servername>.sinusoid instead of <servername>/sinusoid

As a PI SQL Framework end user, I need to be able to distinguish between event frames generated by PI Batch Interfaces from different sites or data sources by filtering my query on the name of an event frame extended property.
PI Batch Interfaces store the unique ID of the data source as the name of an extended property in the event frames they generate. When multiple PI Batch Interfaces write to the same AF Database, the extended property name can be used to distinguish between event frames from different data sources or sites.

It is already possible to create an instance of an existing AF Element Template by using the powershell cmdlet Add-AFElement with the -AFElementTemplate option. The element is then created in the AF tree, however if there are tag creation rules defined in the template, the tags are not created until you manually perform an "Create or Update Data Reference" using the PI System Explorer. It should be possible to trigger "Create or Update Data Reference" via Powershell as well, either by an additional option of the Add-AFElement cmdlet or by a separate cmdlet.

When you alter a view with many attributes, there is a characters number limitation that prevents you from seeing the total content of the view, so basically you cannot edit it because it's kind of "corrupt".

The blog post linked below urges customers to disable TLS 1.0 and TLS 1.1 but also mentions that PI Web API supports them.
https://pisquare.osisoft.com/s/Blog-Detail/a8r1I000000GvqGQAS/tls-best-practices-for-pi-web-api

Please drop support for TLS 1.0 and TLS 1.1 from PI Web API to force customers to use a secure configuration.

Really need to be able to send annotations to PI Tag Values through PowerShell.

The current version of PI DAS (RTQP Engine) does not support local variables. It causes rather clumsy constructs in some instances.

PI DAS (RTQP Engine) 2018 SP3 Patch 1 lacks support for type casting input parameters of a table valued function. For example. this simple example fails to create a table valued function:

CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataStringOverload]
(
@StartTimeIn String,
@EndTimeIn String,
@TimeStepIn String
)
AS
SELECT * FROM MOMS.fact.getInstrumentOperationalData(
CAST(@StartTimeIn As DateTime)
,CAST(@EndTimeIn As DateTime)
,CAST(@TimeStepIn As TimePeriod)
)

The following example fails in similar fashion:

CREATE FUNCTION [MOMS].[fact].[getInstrumentOperationalDataStringOverload]
(
@StartTimeIn String,
@EndTimeIn String,
@TimeStepIn String
)
AS
SELECT * FROM MOMS.fact.getInstrumentOperationalData(
DateTime(@StartTime)
DateTime(@EndTime)
TimePeriod(@TimeStep)
)

Error message: The table-valued function definition is not supported.

If you run

pIServer.StateSets.Add(aFEnumerationSet);
afEnumerationSet.CheckIn();

The set will not be checked in if the PIServer of the AFEnumerationSet is not the same as the PIServer you are checking into.

Instead you have to do:

AFEnumerationSet newSet = new AFEnumerationSet(setToCopy.Name);
foreach (AFEnumerationValue aFEnumerationValue in setToCopy) newSet.Add(aFEnumerationValue); destinationSets.Add(newSet);
setToCopy.CheckIn();

Please automate that functionality.

I would like to perform AF Searches that return results based on Attribute trait filtering. More specifically, I would like to search for Elements that contain Location trait Attributes, so I can query more easily for assets that have a Location trait. I currently rely on Element Categories or Element Template filtering, but those filters do not always match the search results I am looking for.

As a PI Web API administrator, I would like to see errors logged when PI Web API fails to load any attributes because they are not marked as configuration items. This will decrease required troubleshooting for these issues.

Add a method that can be used to sort the IEnumerable<PIPoints> returned by AFSDK's FindPIPoints() method. This method should allow the option of sorting on any desired PI Point Attribute.

Currently the PI Web Api Joined, delivers the data in a json format which is not really "Power BI" friendly , it would be helpful to have a format where all the datavalues from the subordinated are in the same json object of the base.

Internal AF table has been updated using AF versioning system, however retrieving it whole with PI Web API only works for current version: GetData method from Table controller (GET tables/{webId}/data) does not accept a time parameter.
Workarounds involve creating Table Lookup Data Reference attributes or joining all table versions adding columns for time range to be later filtered out.