Troubleshooting Connection Issues

Issue: Administrator has not enabled Google Sheets support

After installing the extension and connecting to your business process, if you open the Home panel and get an error message stating "Administrator has not enabled Google Sheets support for this instance", then you cannot use Smart View in Google Sheets.

As a prerequisite, your Service Administrator needs to enable the Smart View Extension for Google Sheets in the web application settings for every business process that you want to connect through Smart View in Google Sheets. For more information, see Enabling the Smart View Extension for Google Sheets in Getting Started with Oracle Smart View for Google Workspace.

Issue: Permissions not provided to Google Workspace

After clicking Connect, you may get an error message stating "You do not have permission to call UrlFetchApp.fetch. Required permissions: https://www.googleapis.com/auth/script.external_request. For more information, see https://developers.google.com/apps-script/guides/support/troubleshooting#authorization-is".

It indicates that you have not provided Google Workspace the required permissions while installing the Smart View extension. To resolve this connection error, review and provide the required permissions as described in Installing Smart View in Getting Started with Oracle Smart View for Google Workspace.

Issue: Frequent prompts to sign in and reauthenticate

To avoid session expiry and signing in to your business process frequently from Google Sheets, do the following:

Append offline_access in Scope:

In the Scope field, ensure that offline_access is appended toward the end. If not, add as a space after ::all and then add offline_access.

For example, urn:opc:serviceInstanceID=<SERVICE_INSTANCE_ID>urn:opc:resource:consumer::all offline_access

Appending offline_access enables you to obtain new access tokens after your usual tokens expire, thus reducing reauthentication and frequent sign-ins.

If offline_access is not appended in the Scope field, then on clicking Connect, a message appears "Access will not be refreshed after session expiry as offline_access is not added to Scope. Continue session without generating refresh tokens?". Click Yes, to continue connecting without generating refresh tokens. In this case, you will be prompted to authenticate again after session expiry. Click No, to go back and append offline_access in the Scope field.

Allow token refresh:

Ensure that your service administrator has enabled automatic generation of refresh tokens by enabling Allow token refresh as part of the IDCS application creation process.

To select this option in the Oracle Cloud Console, go to Identity domains and click Integrated applications. Click your IDCS application link, and in the OAuth configuration tab. Click Edit OAuth configuration and under Resource server configuration, enable Allow token refresh.

If offline_access is appended in the Scope field but the service administrator has not enabled refreshing of tokens required to prevent session expiry, then on clicking Connect, an error message appears "Service Administrator has not enabled refreshing of access tokens for this instance". You can still continue connecting to your business process without automatic token refresh. by removing the appended offline_access in the Scope field.

See Knowledge Article on My Oracle Support (MOS): Update OAuth 2.0 Configuration and Obtain a New Refresh Token for Oracle Cloud EPM (26.07) to Resolve - 401 Unauthorized Error.

Issue: Cannot connect automatically after session expiry

While working in Google Sheets, if a session expires while you are performing Smart View operations, then an error message appears "Session expired. Cannot connect automatically as refresh token was not generated for this instance. Connect by signing in again". This happens when refreshing of tokens is not enabled.

You can sign in and reauthenticate again to continue working with Smart View in Google Sheets. Please review if your previous operation was performed properly, or perform it again, if required.

Issue: Incorrect Username or Password Error

While using basic authentication, you may get an error about incorrect username or password either while connecting to your business process or while performing Smart View operations. You cannot reset the password in Smart View.

To reset your password, log in to the web application of your business process and change it. Then, try logging in with the new password in Smart View.