openIndexData()
2. Parameters
| Name | Type | Description |
|---|---|---|
|
|
Open in a new tab (webclient; ignored by the rich-client bridge — it has no equivalent there). |
|
|
|
|
|
The object id (osId). |
|
|
The object type id. Improves performance on the webclient; not supported by the rich-client bridge (not sent there). |
3. Per-environment behavior
| Environment | Behavior |
|---|---|
webclient |
Posts |
rich client |
|
standalone (or still detecting without a wire) |
No host reply path exists — the call rejects (bounded) with the
|
4. Examples
await dashlet.openIndexData({ inNewTab: false, mode: 'view', objectId: '1024' });
The string-based equivalent (identical dispatch core) is
dashlet.call('openIndexData', [false, 'view', '1024']) — the positional
array form of the same options.
5. Errors
-
TypeError— an invalid (missing/empty/non-numeric)objectIdin the rich client: the id is coerced to the bridge’s numeric form, and empty or non-numeric ids are rejected descriptively instead of silently opening object 0. -
Error('dashlet destroyed')— the dashlet was destroyed before the call. -
TimeoutError— bounded no-reply in standalone, or a host that never answered withintimeoutMs. -
The host’s
{ error }payload — when the host reports a failure on the webclient method call.