Resetting Fields

Hi
I have a form with a lot of fields in it. I need the fields to be reset when a drop down field called Action Requested is selected.
I've tried adding the "Reset a form" action in the drop down properties but its not working. When I'm in the Preview view of the form and go to select an item from the Action Requested drop down it now allows me only to click on the dropdown and present the list not select anything in it as it apears to be executing the reset immediately. I would like to be able to reset the form regardless of what item is selected, after the item has been selected.
I would be grateful for any ideas.
Cheers
Michael

Hi Gilad, probably not has a fair bit of sensitive stuff in it. Is there some basic script I can put into the droup down field to trigger resetting the other fields once an item in the list is selected?

Similar Messages

Can the reset field button be moved or disabled?

I have adobe reader for ios7 and the reset field button is very easy to hit by accident. You lose all of your information and it is extremely frustrating! If it cannot be moved or disabled can you at least make it so you are prompted for a verification before it wipes out ALL of your information!

Yes. For the "Reset Field" button in the toolbar above the soft keyboard, we are planning to add a confirmation dialog ("Are you sure...?") in a future release, which should prevent users from accidentally resetting/clearing data in a field.
Please note that if a "Reset" or "Clear" button is embedded in a PDF form, it's a responsibility of the author of the PDF form to add a prompt for users.
Thank you for the feedback.

When to reset fields in a custom insert page?

Hi
In Apex 3 I have a page with fields to insert a new record. The first time the page is loaded (clicking a button in another page) I reset all the fields using a Before Header process (so the user doesn't see the previously entered data). The user can then insert data in the fields and click the "Add record" button.
Using conditional branches, on submit I control if the page branches to the calling page or to itself, depending on the success of the operation.
The problem is that, if the operation fails, when the page reloads all the data the user entered is cleared, instead of remaining there to be corrected!
This must be something stupidly basic but I have no idea how to handle it. What is the standard/recommended way to achieve this? Any suggestions will be welcome!
Thanks
Luis

Hi Denes
Yes, the setting is "Only when current value in session state is null".
However, none of both available options for that property is what I need. When the user navigates to that page from another page I want the items to be reset. However, if the page reloads because the processing failed (i.e. the page branches to itself), I want the items to keep their previous values so the user may correct them.
To solve it, I created a page variable called "reset" that indicates that the page variables must be reset and should be set to Y by the calling page. I set it to N in a Before Header process so if the page reloads the variables will not be reset.
But I am not sure if this is the correct way to implement this or if there is a simpler way, because I am sure this must be something very common and trivial for web applications (to which I am quite new).
Thanks
Luis

Reset Field Sequence Value based on Insert OR update on that field

Hi Experts,
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> WITH TAB AS
2 (
3      SELECT 1 ID,2 SEQ FROM DUAL UNION ALL
4      SELECT 2 ID,1 SEQ FROM DUAL UNION ALL
5      SELECT 3 ID,4 SEQ FROM DUAL UNION ALL
6      SELECT 4 ID,3 SEQ FROM DUAL
7 )SELECT * FROM TAB ORDER BY SEQ
8 ;
        ID        SEQ
         2          1
         1          2
         4          3
         3          4
SQL>If i insert or update any of the existing field (SEQ) value, the other values in the field (SEQ) has to
be resetted, like
INSERT INTO TAB VALUES(5,1);
Expected Result:
        ID        SEQ
      5         1
         2          2
         1          3
         4          4
         3          5
SQL>
How can i achieve this?
Thanks,

looks like you might be looking for a custom sequence manager.
you might want to consider using a trigger to do this.
unfortunately if you use just one trigger you will probably get a mutating exception.
so you may need to do a multiple trigger approach
make a place to hold the rows you want to look at
i called mine tad_mgr
CREATE OR REPLACE PACKAGE TAD_MGR IS
* This package spec holds the row ids of the tad table to be used in the 3 trigger approach
type ridArray is table of tab.ID%type index by binary_integer;
newRows ridArray;
empty ridArray;
END;
/your 1st trigger clears out any left over rows you have.
CREATE OR REPLACE TRIGGER TAB_1ST
    before INSERT of ID ON TAB
declare
* This is the 1st trigger in 3 trigger approach to manage seq cds on the tad table
begin
                TAD_MGR.newRows := TAD_MGR.empty;
end;
/your second triggers puts your new or updated row into the container
CREATE OR REPLACE TRIGGER TAB_2ND
BEFORE INSERT
OF ID ON TAB REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
declare
This is the 2nd trigger in 3 trigger approach to manage seq cds on the tad table
begin
             TAD_MGR.newRows( TAD_MGR.newRows.count+1 ) := :new.id;
end;
/finally your last trigger does the updates.
CREATE OR REPLACE TRIGGER TAB_3RD
AFTER INSERT OF ID ON TAB
declare
This is the 3RD trigger in 3 trigger approach to manage seq cds on the tad table
aSEQ tab.seq%type;
aId   tab.id%type;
begin
for i in 1 ..TAD_mgr.newRows.count loop
    select ID, SEQ into aId, aSeq from tab where id = taD_mgr.newRows(i);
    for c in (select id, seq FROM tab where seq >= aSeq and id != aid ) loop
        update tab
        set seq = c.seq + 1
        where id = c.id;
    end loop;
end loop;
           taD_mgr.newRows := taD_mgr.empty;
   end;
/I just did this for the insert just as an example but you can change the triggers to insert or update and change the logic accordingly
Edited by: pollywog on Apr 12, 2010 7:14 AM

Reset button does not reset field color.

Can't find the solution.
I have scripts that highlight the field background color if the value is out of range. Also, resets the color back if the range is OK. This works just fine.
When I reset the form (with button), the field values reset OK, but the field color stays highlighted if that was the state.
The form initially opens with no hightlighting. How do I reset the form values and remove the highlighting?
Thanks,
Wendell

Srini,
I copied a field from my form to your form and the color reset OK. There must be problem with my form structure.
I've only put in two rows of fields to test before I populate the whole form.
The column "Aged Reconciled" highlights yellow if any value other than zero is present. This impacts the column to the right that also is wanting only zero and will highlight in red. If you enter zero in "Aged Reconciled" the highlighting turns off for both fields.
https://acrobat.com/#d=nJ2EpEQ0XT0vGZ8samQHEQ
Thanks for your help!
Wendell

Reseting field properties

I created a Button with a simple reset
// ask question and capture response
cResponse = app.alert("You are about to reset this form. Do you want to proceed?", 2, 2);
if(cResponse == 4) {
// Yes response - then clear the form
this.resetForm();
I just found out that it resets only the value property of the fields but not their default properties like "hidden" or "readonly". Of course, some field on which this property is "calculated" do get back to default but not those that were included in a blur event for example.
Is the only way out of this to add a hidden text field with a calculate script whenever I need to change those properties in case the user would hit the reset button?
Like
onBlur
sometextfield.value = "OFF"
then in the calculate script of the text field
if event.value == "OFF"{
allfields.hidden = true
else{
allfields.hidden = false;

Yes, when you reset a form it simply sets the (specified) fields to their default values. If you use field events to control other fields in some way, you will have to replicate that with more than a simple resetForm statement.

Reset fields

I have a Drop down box that controls several visible/hidden subforms..
MY problem is when the user starts to enter data into the fields and discovers he/she into the wrong section,
how I can reset the entered data(auto) when I am selecting a new item FROM the DD?
If I select a new item and later I back to my first choice still the data is there!
Thanks

You can use the resetData method and pass the field name as the argument..
xfa.host.resetData("xfa.form.form1.TextField1,xfa.form.form1.TextField2");
If you want to do for all the fields inside a subform, then loop thru the nodes in subform and if the Type of the node is field, then pass the name to the above method.
Thanks
Srini

Reset field upon submit

Hi, I have a search field, which once the page has been
submitted I would like to be reset back to the default value, so
that when the page loads up with the query results it has been
reset to default value, how do I do this please? (I already have
onClick in use on the submit button)...
Thanks

Yes it does, I use the form to filter query data. I have temp
fixed it by having preserve data="No", but i kind of liked it
preserving as the date fields remained. So if there is another way
then great.
Since my post, I have added a checkbox to my form, so if they
tick it the query includes some more criteria, however, it works,
but then If I sort again but with the tick box unchecked it still
thinks its checked. Can I write something like <cfif
#form.checkbox# = 'value'> instead of isDefined, would that be
more efficient...?
Thank you for your reply

Resetting fields in Visual Composer

Hi experts,
My requirement is, depending on the field value, I should change the color of the text. I could change the color of the text but i have to reset the field before displaying next value.
Ex:
In a form one field and a button is there.
1.If I enter the value as "Green" and press the button then it should display the text in Green color
2.If I enter the value as "Red" and press the button then it should display the text in Red color
The problem is, whenever I enter the value and press the button it shows the previous color. But if i put another button and reset the field it is working fine.
But, I should get the result in single button click(i.e. i should reset the field and change the color).
Valuable results will be awarded points.
Thanks in Advance
suba

Hi Suba,
maybe this wiki entry helps:
<a href="https://wiki.sdn.sap.com/wiki/display/VC/Resettingfield">https://wiki.sdn.sap.com/wiki/display/VC/Resettingfield</a>
Best Regards,
Marcel

Modify a script to reset fields selectively in a multiform document

The enclosed script allows to clear forms selectively page by page in a multiform document.
But the script is very limited because asks to change in each page where is inserted a new page number for the «resetFieldsOnpage(n) variable.
In a 100 pages document it is a a non-sense task, involving many steps:
go to page
touch the clear field
right mouse /properties
choose actions
select run a java script
edit the Java script
now change the number page
close
Perhaps it is possible to have a real script assigned to the same field (duplicated in all pages) that allows Acrobat understands that the button used is related to a specific page and the clearing will only affect that one.
Thanks.
function resetFieldsOnPage(p) {
    var fields = [];
    for (var i=0; i<this.numFields; i++) {
        var f = this.getField(this.getNthFieldName(i));
        if (f==null) continue;
        if (f.page==p)
            fields.push(f.name);
    this.resetForm(fields);
resetFieldsOnPage(0);

Hi, good point.
But, before, something happened here.
When I was testing the script and using it , immediately opens the script debugger window with a lot of stacks and info!
The form process is stopped.

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, perform the following activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

Using Javascript to reset a form on document load

I am trying to reset all field vaules on a acrobat form to the default values, when the form is initially loaded. I am trying to use the resetForm() method in a document level script, but not having any luck.
I have been able to reset fields after user inputs such as a button that resets the form, or a script the will reset a form prior to importing field data... but I need to ensure all data is removed from the form when the form first loads
Any ideas?

I believe you mean a document level JavaScript, Entering Document Level Scripts, since a Folder level script would require the placing of the code into one of the Acrobat Application's JavaScript folder on the user machine, Entering Folder Level Scripts. Placing the JS code as a Document Level Sept will clear the form when the form is opened. One could also use the Page Open action if additional code is added to prevent re clearing the form if part of a multi page document and one navigates back to the original page.
You should also consider turning off auto complete and auto caching of form data.
Minimizing Exposure of Personal Information on Public Computers

How do I set blank data to date field in pdf form ?

Dear Sir,
I made PDF form by Acrobat X on Windows PC and then,
read the pdf form by acrobat reader on iPad.
Date field is included in the form.
The Acrobat version is 10.1.6 .
The acrobat reader version is 10.5.0 .
First, I put the wrong date data to the date field.
So, I tried to clear the date field.
I want to put the blank data to the date, but I think
there are no way to put the blank data on iPad
I would like to know how to reset the date data.
If that helps, I tried to the same thing on Android.
I could put blank data to the date field by BS key.
Sincerely,
PV NEXT CO., LTD.
Kiyonobu Matsuo
PVネクスト株式会社

Here is how to clear the Date field on the Ipad.
NOTE: In order for this to work that has to be another TEXT field in the PDF to get the keyboard to pop-up.
Click on Text field (this is to get the regular keyboard on screen)
Click on Date field (date spinner control will show up)
Click on SAME DATE field (spinner control will disapper)
Click on "Reset Field" on top of keyboard (date field will now be empty)
Click any where on PDF that is not another Date field (keyboard will disappear and date field will be empty)
Bingo! your free and clear.

Reset Button in Creator 2 does not work properly

Hi,
I have created a form to create a user profile using Studio Creator Update 1. It has a few text fields. It has a checkbox "Add more details" which when clicked enables a few more text fields. At the end of the form I have a Submit and a Reset button.
Now, when I fill the form (without touching the 'Add more details' checkbox) and click the Reset button, the text fields becomes blank as expencted.
Lets say I enter some values in a few text field, then I check the checkbox, some more fields gets enabled (i do this inside the processValue method). Now, if I click Reset button, the form does not get blank. Even worst, if I change the already typed text field values and click Reset, these text field gets repopulated with original values. Is this a bug or a feature.
Any solution for this problem is greatly appretiated.
Regards,
Shastri.

hi i am also developing similar application which have some textfields and submit and reset fields. Please help me how you are sending data to the database table and how you are editing the required rowgroup elements into that submit form from database. Please help me out by giving an example. I alos gone through the inserts_update_delete tutorial in java studio creator. Please give some example of code.
Actually i am using SQL Server database. Please i tried but it is showing cannot add new employee details. null. Please give me some instances of code for inserting , deleting and retrieving the data. Please help me out i am trying sincerely but it is really get frustrated.
Thank you in Advance.

Resetting Fields

Similar Messages

Maybe you are looking for