My Oracle Support Banner

Oracle Public Sector Permits Cloud :Unable To Map A Custom Field To A Fee Input (Doc ID 2833975.1)

Last updated on JANUARY 14, 2022

Applies to:

Oracle Public Sector Permits Cloud Service - Version 11.13.21.10.0 and later
Information in this document applies to any platform.

Goal

On : 11.13.21.10.0 version, Permits

Unable to map a custom field to a fee input

Expected:
All fields on the intake form will be available to be mapped to appropriate fee inputs.

Actual:
Some custom fields are not showing up in the fee mapping dropdown.

Steps taken:
1. Tried to map existing custom LOV to string fee input field.
2. Removed the existing field, saved and published form.
3. Added new version of the custom LOV field that is required to be on the intake form. Saved and published form.
4. Tried to map the replacement version of the custom LOV to the string fee input field. It still doesn't appear in the dropdown.


 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.