Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Data View

Data View

The
openrecord;dv
operation is used to open a data view.
The
subjectAreaID
identifies the subject area, and
param1
identifies the record. As with SIF APIs, a record can be identified either by rowid or by system name and source key. When using source key, be sure to include any leading or trailing spaces in the value.
Additionally,
param2
can be used to specify
xref
,
history
,
duplicates
to open the Data View with the
Cross References
,
History
, or
Find Duplicates
screens.
Examples:
http://<host>[:<port>]/bdd/?deeplink=openrecord;dv;test/Customer;rowid:268 http://<host>[:<port>]/bdd/?deeplink=openrecord;dv;test/Customer; systemName:SFA,sourceKey:CST1160 http://<host>[:<port>]/bdd/?deeplink=openrecord;dv;test/Customer;rowid:268;xref
Merged records are a special case. If you merge a record with another record, the merged record has the rowid of the surviving record. You can, however, continue to use a bookmark URL that references the non-surviving rowid. In this case, the URL is redirected to the merged record rowid. For example, let's say that you merge two records with rowids 1 and 2, and the merged record has the rowid 1. If you use a bookmark URL and specify rowid 2, the link is redirected and retrieves the merged record with rowid 1.

0 COMMENTS

We’d like to hear from you!