GetViewDlgSaveInfoAsync Method
Overloads
GetViewDlgSaveInfoAsync() |
Returns information about the position of the tables in the data model viewer. |
|
GetViewDlgSaveInfoAsync(AsyncHandle) |
Returns information about the position of the tables in the data model viewer. |
|
GetViewDlgSaveInfoAsync<T>(AsyncHandle, Func<Response, T>) |
Returns information about the position of the tables in the data model viewer. |
GetViewDlgSaveInfoAsync()
Returns information about the position of the tables in the data model viewer.
Declaration
Task<TableViewDlgSaveInfo> GetViewDlgSaveInfoAsync()
Returns
Type | Description |
---|---|
System.Threading.Tasks.Task<TableViewDlgSaveInfo> |
Remarks
The position of the broom points and the position of the connection points cannot be retrieved in Qlik Sense.
GetViewDlgSaveInfoAsync(AsyncHandle)
Returns information about the position of the tables in the data model viewer.
Declaration
Task<TableViewDlgSaveInfo> GetViewDlgSaveInfoAsync(AsyncHandle asyncHandle)
Parameters
Type | Name | Description |
---|---|---|
AsyncHandle | asyncHandle |
Handle to asynchronous method request |
Returns
Type | Description |
---|---|
System.Threading.Tasks.Task<TableViewDlgSaveInfo> |
Remarks
The position of the broom points and the position of the connection points cannot be retrieved in Qlik Sense.
GetViewDlgSaveInfoAsync<T>(AsyncHandle, Func<Response, T>)
Returns information about the position of the tables in the data model viewer.
Declaration
Task<T> GetViewDlgSaveInfoAsync<T>(AsyncHandle asyncHandle, Func<Response, T> onResult)
Parameters
Type | Name | Description |
---|---|---|
AsyncHandle | asyncHandle |
Handle to asynchronous method request |
System.Func<Response, T> | onResult |
Continuation function |
Returns
Type | Description |
---|---|
System.Threading.Tasks.Task<T> |
Type Parameters
Name | Description |
---|---|
T |
Remarks
The position of the broom points and the position of the connection points cannot be retrieved in Qlik Sense.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!