Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 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
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Pop-up are giving ppr issue after migrating to 12.2.1

<af:commandButton id="shtasr" text="#{msg['go.alsoServesByRevDate']}" immediate="true"
action="#{attrs.sheetHandler.alsoServesBO.alsoServesByRevDate_click}" partialSubmit="true"
visible="#{!attrs.sheetHandler.isEnrChartItem}" partialTriggers="pt1:toolbar:claimBtn"/>
<af:spacer width="1px" height="1"/>
it says reference ID pt1:toolbar:claimBtn does not exist. how to resolve this issue in 12.2.1
Answers
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,572 Red Diamond
Well, you use the edit function on the property and select the component (the toolbar button) again.
Timo
-
we have just migrated this application but we are not able to find this component any suggestion we might be doing wrong
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,572 Red Diamond
Maybe the component has been removed in the old version but the partialtrigger was left as is. In the old version. This wasn't a problem (the target is just ignored) but now you get some kind of error to make you aware of the situation.
Remove the partialTigger and test your application. If you don't find anything not working, my assumption is right and you are done.
Timo