Discussions
Categories
- 385.1K All Categories
- 2.6K Data
- 605 Big Data Appliance
- 2K Data Science
- 452.2K Databases
- 222.4K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 576 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 575 SQLcl
- 4K SQL Developer Data Modeler
- 187.8K SQL & PL/SQL
- 21.5K SQL Developer
- 12 Data Integration
- 12 GoldenGate
- 297.7K Development
- 3 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 294.4K Development Tools
- 118 DevOps
- 3.1K QA/Testing
- 646.5K Java
- 30 Java Learning Subscription
- 37K Database Connectivity
- 185 Java Community Process
- 107 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 174 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 587 LiveLabs
- 41 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 197 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 240 Portuguese
add Validation when inserting in ADF table
Hello,
I need some help.
I'm a newbie and I'm using JDeveloper 12.2.1.4.0.
How can I add validation in ADF table when inserting? My requirement was if the status of the person number is NEW and PENDING with same cycle, it will not insert to avoid duplication and it will insert only if the status is already set to PROCESSED
For example,
The UI page
clicked the create button
after inputting the data, when I click save button it should not insert because the person number and the cycle is already existing the table
This is the functionality of the buttons
Thank you.
Best Answer
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,930 Red DiamondThis should be done in the DB to avoid wrong data in the db. There you can add a check constraint to check if a record matches your criteria the throw a DB error. This error is picked up from the framework and published to the UI.
Another method would be to do this in java. Here you can add a business logic and check the criteria. See
Timo
Answers
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,930 Red Diamond
This should be done in the DB to avoid wrong data in the db. There you can add a check constraint to check if a record matches your criteria the throw a DB error. This error is picked up from the framework and published to the UI.
Another method would be to do this in java. Here you can add a business logic and check the criteria. See
Timo
-
You can create an Alternate Key Constraint on the EO and then use the UniqueKey Validation to validate the key value at commit time. Detail at https://docs.oracle.com/middleware/12212/adf/develop/GUID-92542726-9FC2-435D-8BAC-F140CB0DC579.htm#ADFFD413
-
-
Could be because an Alternate Key is not defined. Is an Alt Key defined? Please refer https://docs.oracle.com/middleware/12212/adf/develop/GUID-631716A4-95D2-41A0-A56B-FB168F5268AA.htm#ADFFD212
-
Hello, I already added the Alternate Key and selected the UniqueKey Validation. But how can i put validation if the status is NEW/PENDING with same person number and cycle, it will throw an error or else it will insert only if the status is already set to PROCESSED
-
Since creating an alternate key essentially creates indexing on the table in the database. It will fail if duplicate records are already there. To remove duplicates either use advanced find to manually delete or update records or duplicate detection job to delete the record. This usually happens when multiple records exist that have the same combined alternate key in the target system. Run an advanced find for the fields that make up the alternate key on the entity in question and I'm sure you will find duplicate results. Changing the values of one of those duplicate records (across every pair of duplicates) will allow the key to be created once there are no duplicates.
-
Thanks for your help. I used the method validator for validating the ADF table.
