![](https://cdn.userecho.com/characters/77.png?1)
Query T001F065_ACTUAL_POSITION_NO in IdB 5.x Aurion Position query
Client DBA was able to determine that the Aurion position connector actually runs 3 queries in IDB version 3 and 5.
The first and third are identical but the second script is totally different.
In version 3, the position appears to be retrieved from "T001F065_ACTUAL_POSITION_NO" whereas in version 5 appears to try to determine position information from "T101F005_POSITION_NO".
Is it possible to have the position query retrieve data from "T001F065_ACTUAL_POSITION_NO" in IdB 5.x?
Answer
![](https://cdn.userecho.com/characters/65.png?1)
What query are you referring to? If it's the Aurion query - it's completely up to you what comes back. Just change the query in the query editor.
![](https://cdn.userecho.com/characters/77.png?1)
So it's independent of the connector? They can make any changes they like to this query?
![](https://cdn.userecho.com/characters/65.png?1)
https://unifysolutions.jira.com/wiki/display/IDBAUR51/Specifications
So it's independent of the connector?
Yes, the connector points to whatever query you like. That's why there is the schema mapping - so that the query fields are mapped to the connector fields.
They can make any changes they like to this query?
Correct - in the Aurion query tool.
![](https://cdn.userecho.com/characters/77.png?1)
OK, It sounds as though there is a misalignment between dev & prod. Will ask them to update the environment.
Customer support service by UserEcho
OK, It sounds as though there is a misalignment between dev & prod. Will ask them to update the environment.