An error occurred when validating the descriptive flexfield

Rated 3.89/5 based on 989 customer reviews

To continue using this form, have the system administrator either remove all : BLOCK.FIELD references, or turn off wide area operation by setting the profile option - Flexfields: Validate on Server to N.For example, an airline manufacturer may require specific attributes for its orders that aren't predefined.Using a flexfield for the order business object, you can create and configure the required attribute.

Lets say for Responsibility-1 this profile is set to XX, and for Responsibility-2 this profile is set to YY, and for a special user this profile is set to value ZZ. Hi Anil I have a doubt regarding how to change the context using or form personalisation?

Two of the PO Distribution DFF Segments have a Value Set with : Block.field reference.

The value set uses the :block.field as seen in the PO Entry Form (block name is different on PO Summary Distributions Form). However, there is an error when accessing PO Distributions from the PO Summary form. I tried that but the forms are still accessing the Global Data Elements Segments. CURRENT_FORM Context Field Values Global Data Elements (original defintion) POXPOEPO (defined two segments attribute 1 and 2 with the value set with :block.field reference.) POXPOVPO (defined two segments without Value Sets since this is a view only form) What am I doing wrong and how do I make this work? Thanks, Neerja Business requirement: FND Lookup Form - Common Lookups The DFF in Lookup Values has 2 contexts, freight and ship method. DFF should show both the contexts so that user may set or unset the values for any context value.

In this scenario, you can design your descriptive flexfield on a System variable context. There is only one context reference field available per Descriptive Flexfield. When we query Address DFF in Receivables, I am trying to add my custom valuesets for the code AS_DEFAULT segments for City, State, County and Postal Code. thanks anil Hi Anil thnx for the reply so if the context is dependent on profile or global variable, we have to use tht profile in context reference field and populate the profile value programmatically using custom.pll/fp. Regards Kishore The Invoice Line Information DFF is used in AR Transactions Form and AR Credit Transactions form.

If you choose to have your DFF context sensitive on a profile option, then you will have to live with it forever(ah should I say fusion-when D2K forms are gone). When i choose Postal code based on that other columns needs to be populated. I need to set a Reference Field of BATCH_SOURCE name in both the Forms. Thanks Prasad Anil, I recently came across your blog and am very impressed with the work you are doing.

Leave a Reply