/AWS1/IF_QST=>DESCRIBEACCOUNTCUSTOMIZATION()¶
About DescribeAccountCustomization¶
Describes the customizations associated with the provided Amazon Web Services account and Amazon
Quick Sight namespace. The Quick Sight console evaluates which
customizations to apply by running this API operation with the Resolved flag
included.
To determine what customizations display when you run this command, it can help to visualize the relationship of the entities involved.
-
Amazon Web Services account- The Amazon Web Services account exists at the top of the hierarchy. It has the potential to use all of the Amazon Web Services Regions and Amazon Web Services Services. When you subscribe to Quick Sight, you choose one Amazon Web Services Region to use as your home Region. That's where your free SPICE capacity is located. You can use Quick Sight in any supported Amazon Web Services Region. -
Amazon Web Services Region- You can sign in to Quick Sight in any Amazon Web Services Region. If you have a user directory, it resides in us-east-1, which is US East (N. Virginia). Generally speaking, these users have access to Quick Sight in any Amazon Web Services Region, unless they are constrained to a namespace.To run the command in a different Amazon Web Services Region, you change your Region settings. If you're using the CLI, you can use one of the following options:
-
Use command line options.
-
Use named profiles.
-
Run
aws configureto change your default Amazon Web Services Region. Use Enter to key the same settings for your keys. For more information, see Configuring the CLI.
-
-
Namespace- A Quick Sight namespace is a partition that contains users and assets (data sources, datasets, dashboards, and so on). To access assets that are in a specific namespace, users and groups must also be part of the same namespace. People who share a namespace are completely isolated from users and assets in other namespaces, even if they are in the same Amazon Web Services account and Amazon Web Services Region. -
Applied customizations- Quick Sight customizations can apply to an Amazon Web Services account or to a namespace. Settings that you apply to a namespace override settings that you apply to an Amazon Web Services account.
Method Signature¶
METHODS /AWS1/IF_QST~DESCRIBEACCOUNTCUSTOMIZATION
IMPORTING
!IV_AWSACCOUNTID TYPE /AWS1/QSTAWSACCOUNTID OPTIONAL
!IV_NAMESPACE TYPE /AWS1/QSTNAMESPACE OPTIONAL
!IV_RESOLVED TYPE /AWS1/QSTBOOLEAN OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_qstdscaccustization01
RAISING
/AWS1/CX_QSTACCESSDENIEDEX
/AWS1/CX_QSTINTERNALFAILUREEX
/AWS1/CX_QSTINVPARAMVALUEEX
/AWS1/CX_QSTRESOURCENOTFOUNDEX
/AWS1/CX_QSTRESOURCEUNAVAILEX
/AWS1/CX_QSTTHROTTLINGEX
/AWS1/CX_QSTCLIENTEXC
/AWS1/CX_QSTSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_awsaccountid TYPE /AWS1/QSTAWSACCOUNTID /AWS1/QSTAWSACCOUNTID¶
The ID for the Amazon Web Services account that you want to describe Quick Sight customizations for.
Optional arguments:¶
iv_namespace TYPE /AWS1/QSTNAMESPACE /AWS1/QSTNAMESPACE¶
The Quick Sight namespace that you want to describe Quick Sight customizations for.
iv_resolved TYPE /AWS1/QSTBOOLEAN /AWS1/QSTBOOLEAN¶
The
Resolvedflag works with the other parameters to determine which view of Quick Sight customizations is returned. You can add this flag to your command to use the same view that Quick Sight uses to identify which customizations to apply to the console. Omit this flag, or set it tono-resolved, to reveal customizations that are configured at different levels.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_qstdscaccustization01 /AWS1/CL_QSTDSCACCUSTIZATION01¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
Examples¶
Syntax Example¶
This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.
DATA(lo_result) = lo_client->describeaccountcustomization(
iv_awsaccountid = |string|
iv_namespace = |string|
iv_resolved = ABAP_TRUE
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_arn = lo_result->get_arn( ).
lv_awsaccountid = lo_result->get_awsaccountid( ).
lv_namespace = lo_result->get_namespace( ).
lo_accountcustomization = lo_result->get_accountcustomization( ).
IF lo_accountcustomization IS NOT INITIAL.
lv_arn = lo_accountcustomization->get_defaulttheme( ).
lv_arn = lo_accountcustomization->get_defemailcustizationtmpl( ).
ENDIF.
lv_string = lo_result->get_requestid( ).
lv_statuscode = lo_result->get_status( ).
ENDIF.