About developing for portability
Develop Px Views that you can easily use in multiple scenarios by specifying relative ORDs in bindings and hyperlinks.
Bound label using absolute ORD
For purposes of this discussion, the term portability means reusability. In other words, being able to use the same Px View in different stations without having to edit the ORD properties for bindings and hyperlinks. Another example of portability, is being able to use the same Px view in a controller station and a Supervisor station without having to edit ORD properties. You can develop portable Px views by avoiding the use of absolute ORDs in bindings and hyperlinks. The reason to avoid using absolute ORD properties in Px views is that they are not portable between stations.
The floor plan graphic shown below has a bound label configured with a hyperlink to a detailed graphic for a specific device. You can see that both the ord binding and hyperlink properties use an absolute ord, meaning the value specifies the entire station slot path.

Supervisor absolute ORD
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor/AHU1
JACE absolute ORD
station:|slot:/Drivers/LonNetwork/FirstFloor/points/FirstFloor/SpaceTemp
Bound label using relative ORD

The same relative ORDs can be used in both the JACE and the Supervisor station since it is being applied against different base ORDs
Hyperlink using absolute ORD

In order to use the above graphic in the Supervisor station, you must use NiagaraNetwork proxy points and assign a Px view or by using a Px view export tag.
Absolute ORD in JACE
station:|slot:/Drivers/LonNetwork/FirstFloor
Absolute ORD in Supervisor
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor
Hyperlink using relative ORD

Relative ORD in Px page
slot:..
Base ORD in JACE
station:|slot:/Drivers/LonNetwork/FirstFloor/AHU1
Base ORD in Supervisor
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor/AHU1