Form Field Error when similar names
In Adobe Acrobat X Pro, I receive the following error when I try to change the name of a text field from Company.BS.Condition1.Date to Company.BS.Condition.Date: "A field of a different type already uses this name. Please choose a new name for the field, or change the field type to match the existing field with this name." But, there is no other field with that name. There is a checkbox with a similar name: Company.BS.Condition I must use these particular field names, as they are being automatically populated by a program that is written to use these field names.
Sometimes while creating a form it's structures gets corrupted due to which some users face this difficulty. Here's what you can do fix the issue.
Print the form using Adobe PDF printer (installed with Acrobat) to create a flat file with no fields.
Open the form in Acrobat. Click on Tools-> Forms -> Edit.
Allow the form to self detect the fields.
Place the remaining fields like checkbox, signature fields and text fields.
Close the form editing mode and save the form.
For the Reader users, remember to read extend the form. If the all the users are using Reader XI then it's fine.
To Read extend the form, Open the form in Acrobat, click on "File" -> Save as Other-> Reader Extended PDF-> Enable Additonal features.
I am also attaching the fixed form for your reference.
~Deepak
Similar Messages
-
The field "GLTPC" is unknown, but there is a field with the similar name*
Hi all
When i am running the report painter reports in SAP
i am getting this error .
Syntax error in program SAPFGRWG
in include FGRWGE60
in line 19
Last changed by SAP
Author SAP
The field "GLTPC" is unknown, but there is a field with the similar name
"GLTPC".*
Please help me whenever
Regards,
suchithra
Edited by: Rob Burbank on May 22, 2009 9:00 AMHi All
All 8A group Report painter reports i.e GLPCt table Reports are not executed properly
Can you please help me out
Regards,
suchithra -
Identifying form fields automatically when word doc is imported
Hi
I am trying to convert a word document template to a PDF template using Adobe Live Cycle. There are 7 tables in the Word document. I saved the doc as PDF using Word. When i imported the PDF into the Live Cycle Designer, the form fields ( table rows and cells) are not being identified. All are kind of static text.
However, when i opened the same PDF in Acrobat Pro, i was able to identify the form fields ( using Form > edit fields option).
Is there something similar available in Live Cycle Designer. Can the LCD identify form fields automatically.
Appreciate your help.
Thanks and regards
RamI don't believe this functionality is built into LiveCycle Designer. However, you can start your form in Acrobat (Acroform) then import the PDF into LiveCycle. Keep in mind this is a one way process.
-
Hi All ,
We have a scenario to automatically update the Infopath form(List Form) fields(Field Name and Control) when ever a new Column is created in the SharePoint list. Is it possible to do this? any options or suggestions?
Thanks and Regards,
NandiniHi Nandini,
I am not very sure will this be going to help you. Ideally, it's not so easy to communicate with infopath using object model. But still you can give it a try using below link :
http://social.msdn.microsoft.com/forums/sharepoint/en-US/00125fdc-2115-47ea-8e8b-1ca9e5942f83/update-infopath-form-field-in-event-receiver
I think the above solution is trying to update the field. Addition to that you can try creating a field and control.
Let me know if it helps !!
Thanks -
Check Form for Errors When Digitally Signing?
Greetings,
I am using LiveCycle Designer ES3. The target version of my form is Adobe version 8.
My form is initially completed by a document generator, then forwarded to a reviewer. The reviewer will then use the form to document his/her determinations (approved, disapproved, etc) of the material the document generator submitted for review. Once the reviewer is done with his/her determinations, he/she digitally signs the document using the signature field created in LiveCycle. Once the document is signed, it is locked down and unable to be edited further.
Is it possible to have my form check for oustanding errors when the reviewer attempts to sign? Also, is it possible to not allow the reviewer to sign if errors are present?
Thank you in advance for your help.To clarify, the document generator only fills out a few fields. The reviewer completes the rest of the form, so the reviewer would be the one making the errors.
-
Form validation error when the Table is empty.
Hello Gurus,
I am getting form validation error as soon as the popup is rendered to submit new row.
I am using the this popup to add new row in the table and this is happening only when there no data in the table but it works fine when there is some data in the table.
Screen shot: [http://picpaste.com/adf_error-BAdP8Thv.JPG]
Is there any way can I defer this error till I submit the form. ( which works fine when there is some data in table )
Thanks
Abhijeethere i tested not happend for me.
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1" binding="#{backingBeanScope.backing_untitled8.d1}">
<af:form binding="#{backingBeanScope.backing_untitled8.f2}" id="f2">
<af:messages binding="#{backingBeanScope.backing_untitled8.m1}"
id="m1"/>
<af:popup binding="#{backingBeanScope.backing_untitled8.p1}" id="p1">
<af:dialog binding="#{backingBeanScope.backing_untitled8.d3}" id="d3">
<af:panelFormLayout binding="#{backingBeanScope.backing_untitled8.pfl1}"
id="pfl1">
<af:inputText value="#{bindings.AunitctrlBe.inputValue}"
label="#{bindings.AunitctrlBe.hints.label}"
required="#{bindings.AunitctrlBe.hints.mandatory}"
columns="#{bindings.AunitctrlBe.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlBe.hints.precision}"
shortDesc="#{bindings.AunitctrlBe.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it10}"
id="it10">
<f:validator binding="#{bindings.AunitctrlBe.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlUnit.inputValue}"
label="#{bindings.AunitctrlUnit.hints.label}"
required="#{bindings.AunitctrlUnit.hints.mandatory}"
columns="#{bindings.AunitctrlUnit.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlUnit.hints.precision}"
shortDesc="#{bindings.AunitctrlUnit.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it11}"
id="it11">
<f:validator binding="#{bindings.AunitctrlUnit.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlCostMethod.inputValue}"
label="#{bindings.AunitctrlCostMethod.hints.label}"
required="#{bindings.AunitctrlCostMethod.hints.mandatory}"
columns="#{bindings.AunitctrlCostMethod.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlCostMethod.hints.precision}"
shortDesc="#{bindings.AunitctrlCostMethod.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it12}"
id="it12">
<f:validator binding="#{bindings.AunitctrlCostMethod.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlCostMgmtOpt.inputValue}"
label="#{bindings.AunitctrlCostMgmtOpt.hints.label}"
required="#{bindings.AunitctrlCostMgmtOpt.hints.mandatory}"
columns="#{bindings.AunitctrlCostMgmtOpt.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlCostMgmtOpt.hints.precision}"
shortDesc="#{bindings.AunitctrlCostMgmtOpt.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it13}"
id="it13">
<f:validator binding="#{bindings.AunitctrlCostMgmtOpt.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlCostApprMtd.inputValue}"
label="#{bindings.AunitctrlCostApprMtd.hints.label}"
required="#{bindings.AunitctrlCostApprMtd.hints.mandatory}"
columns="#{bindings.AunitctrlCostApprMtd.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlCostApprMtd.hints.precision}"
shortDesc="#{bindings.AunitctrlCostApprMtd.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it14}"
id="it14">
<f:validator binding="#{bindings.AunitctrlCostApprMtd.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlJocApprMtd.inputValue}"
label="#{bindings.AunitctrlJocApprMtd.hints.label}"
required="#{bindings.AunitctrlJocApprMtd.hints.mandatory}"
columns="#{bindings.AunitctrlJocApprMtd.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlJocApprMtd.hints.precision}"
shortDesc="#{bindings.AunitctrlJocApprMtd.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it15}"
id="it15">
<f:validator binding="#{bindings.AunitctrlJocApprMtd.validator}"/>
</af:inputText>
<af:inputText value="#{bindings.AunitctrlCreBy.inputValue}"
label="#{bindings.AunitctrlCreBy.hints.label}"
required="#{bindings.AunitctrlCreBy.hints.mandatory}"
columns="#{bindings.AunitctrlCreBy.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlCreBy.hints.precision}"
shortDesc="#{bindings.AunitctrlCreBy.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it16}"
id="it16">
<f:validator binding="#{bindings.AunitctrlCreBy.validator}"/>
</af:inputText>
<af:inputDate value="#{bindings.AunitctrlCreDate.inputValue}"
label="#{bindings.AunitctrlCreDate.hints.label}"
required="#{bindings.AunitctrlCreDate.hints.mandatory}"
shortDesc="#{bindings.AunitctrlCreDate.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.id1}"
id="id1">
<f:validator binding="#{bindings.AunitctrlCreDate.validator}"/>
<af:convertDateTime pattern="#{bindings.AunitctrlCreDate.format}"/>
</af:inputDate>
<af:inputText value="#{bindings.AunitctrlUpdBy.inputValue}"
label="#{bindings.AunitctrlUpdBy.hints.label}"
required="#{bindings.AunitctrlUpdBy.hints.mandatory}"
columns="#{bindings.AunitctrlUpdBy.hints.displayWidth}"
maximumLength="#{bindings.AunitctrlUpdBy.hints.precision}"
shortDesc="#{bindings.AunitctrlUpdBy.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it17}"
id="it17">
<f:validator binding="#{bindings.AunitctrlUpdBy.validator}"/>
</af:inputText>
<af:inputDate value="#{bindings.AunitctrlUpdDate.inputValue}"
label="#{bindings.AunitctrlUpdDate.hints.label}"
required="#{bindings.AunitctrlUpdDate.hints.mandatory}"
shortDesc="#{bindings.AunitctrlUpdDate.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.id2}"
id="id2">
<f:validator binding="#{bindings.AunitctrlUpdDate.validator}"/>
<af:convertDateTime pattern="#{bindings.AunitctrlUpdDate.format}"/>
</af:inputDate>
<af:inputText value="#{bindings.RowID.inputValue}"
label="#{bindings.RowID.hints.label}"
required="#{bindings.RowID.hints.mandatory}"
columns="#{bindings.RowID.hints.displayWidth}"
maximumLength="#{bindings.RowID.hints.precision}"
shortDesc="#{bindings.RowID.hints.tooltip}"
binding="#{backingBeanScope.backing_untitled8.it18}"
id="it18">
<f:validator binding="#{bindings.RowID.validator}"/>
</af:inputText>
<f:facet name="footer">
<af:panelGroupLayout layout="vertical"
binding="#{backingBeanScope.backing_untitled8.pgl1}"
id="pgl1">
<af:panelGroupLayout layout="horizontal"
binding="#{backingBeanScope.backing_untitled8.pgl2}"
id="pgl2">
<af:commandButton actionListener="#{bindings.First1.execute}"
text="First1"
disabled="#{!bindings.First1.enabled}"
partialSubmit="true"
binding="#{backingBeanScope.backing_untitled8.cb1}"
id="cb1"/>
<af:commandButton actionListener="#{bindings.Previous1.execute}"
text="Previous1"
disabled="#{!bindings.Previous1.enabled}"
partialSubmit="true"
binding="#{backingBeanScope.backing_untitled8.cb3}"
id="cb3"/>
<af:commandButton actionListener="#{bindings.Next1.execute}"
text="Next1"
disabled="#{!bindings.Next1.enabled}"
partialSubmit="true"
binding="#{backingBeanScope.backing_untitled8.cb4}"
id="cb4"/>
<af:commandButton actionListener="#{bindings.Last1.execute}"
text="Last1"
disabled="#{!bindings.Last1.enabled}"
partialSubmit="true"
binding="#{backingBeanScope.backing_untitled8.cb5}"
id="cb5"/>
</af:panelGroupLayout>
<af:commandButton text="Submit"
binding="#{backingBeanScope.backing_untitled8.cb6}"
id="cb6"/>
</af:panelGroupLayout>
</f:facet>
</af:panelFormLayout>
</af:dialog>
</af:popup>
<af:panelCollection binding="#{backingBeanScope.backing_untitled8.pc2}"
id="pc2">
<f:facet name="menus"/>
<f:facet name="toolbar">
<af:toolbar binding="#{backingBeanScope.backing_untitled8.t3}"
id="t3">
<af:commandButton text="insert"
binding="#{backingBeanScope.backing_untitled8.cb7}"
id="cb7"
action="#{backingBeanScope.backing_untitled8.cb7_action}"
partialSubmit="true"/>
</af:toolbar>
</f:facet>
<f:facet name="statusbar"/>
<af:table value="#{bindings.ApplUnitControlView1.collectionModel}"
var="row" rows="#{bindings.ApplUnitControlView1.rangeSize}"
emptyText="#{bindings.ApplUnitControlView1.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.ApplUnitControlView1.rangeSize}"
rowBandingInterval="0"
filterModel="#{bindings.ApplUnitControlView1Query.queryDescriptor}"
queryListener="#{bindings.ApplUnitControlView1Query.processQuery}"
filterVisible="true" varStatus="vs"
selectedRowKeys="#{bindings.ApplUnitControlView1.collectionModel.selectedRow}"
selectionListener="#{bindings.ApplUnitControlView1.collectionModel.makeCurrent}"
rowSelection="single"
binding="#{backingBeanScope.backing_untitled8.t4}" id="t4"
partialTriggers=":::cb1 :::cb3 :::cb4 :::cb5 ::cb2">
<af:column sortProperty="AunitctrlBe" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.label}"
id="c6" width="105">
<af:inputText value="#{row.bindings.AunitctrlBe.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlBe.tooltip}"
id="it1">
<f:validator binding="#{row.bindings.AunitctrlBe.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlUnit" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.label}"
id="c3" width="105">
<af:inputText value="#{row.bindings.AunitctrlUnit.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUnit.tooltip}"
id="it9">
<f:validator binding="#{row.bindings.AunitctrlUnit.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlCostMethod" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.label}"
id="c9" width="105">
<af:inputText value="#{row.bindings.AunitctrlCostMethod.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMethod.tooltip}"
id="it6">
<f:validator binding="#{row.bindings.AunitctrlCostMethod.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlCostMgmtOpt" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.label}"
id="c1" width="105">
<af:inputText value="#{row.bindings.AunitctrlCostMgmtOpt.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostMgmtOpt.tooltip}"
id="it3">
<f:validator binding="#{row.bindings.AunitctrlCostMgmtOpt.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlCostApprMtd" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.label}"
id="c2" width="105">
<af:inputText value="#{row.bindings.AunitctrlCostApprMtd.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCostApprMtd.tooltip}"
id="it2">
<f:validator binding="#{row.bindings.AunitctrlCostApprMtd.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlJocApprMtd" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.label}"
id="c4" width="105">
<af:inputText value="#{row.bindings.AunitctrlJocApprMtd.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlJocApprMtd.tooltip}"
id="it4">
<f:validator binding="#{row.bindings.AunitctrlJocApprMtd.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlCreBy" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.label}"
id="c5" width="105">
<af:inputText value="#{row.bindings.AunitctrlCreBy.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCreBy.tooltip}"
id="it7">
<f:validator binding="#{row.bindings.AunitctrlCreBy.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlCreDate" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.label}"
id="c8" width="103">
<f:facet name="filter">
<af:inputDate value="#{vs.filterCriteria.AunitctrlCreDate}"
binding="#{backingBeanScope.backing_untitled8.id5}"
id="id5"/>
</f:facet>
<af:inputDate value="#{row.bindings.AunitctrlCreDate.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.mandatory}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.tooltip}"
id="id3">
<f:validator binding="#{row.bindings.AunitctrlCreDate.validator}"/>
<af:convertDateTime pattern="#{bindings.ApplUnitControlView1.hints.AunitctrlCreDate.format}"/>
</af:inputDate>
</af:column>
<af:column sortProperty="AunitctrlUpdBy" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.label}"
id="c7" width="107">
<af:inputText value="#{row.bindings.AunitctrlUpdBy.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdBy.tooltip}"
id="it5">
<f:validator binding="#{row.bindings.AunitctrlUpdBy.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="AunitctrlUpdDate" filterable="true"
sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.label}"
id="c10" width="105">
<f:facet name="filter">
<af:inputDate value="#{vs.filterCriteria.AunitctrlUpdDate}"
binding="#{backingBeanScope.backing_untitled8.id6}"
id="id6"/>
</f:facet>
<af:inputDate value="#{row.bindings.AunitctrlUpdDate.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.label}"
required="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.mandatory}"
shortDesc="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.tooltip}"
id="id4">
<f:validator binding="#{row.bindings.AunitctrlUpdDate.validator}"/>
<af:convertDateTime pattern="#{bindings.ApplUnitControlView1.hints.AunitctrlUpdDate.format}"/>
</af:inputDate>
</af:column>
<af:column sortProperty="RowID" filterable="true" sortable="true"
headerText="#{bindings.ApplUnitControlView1.hints.RowID.label}"
id="c11" width="105">
<af:inputText value="#{row.bindings.RowID.inputValue}"
label="#{bindings.ApplUnitControlView1.hints.RowID.label}"
required="#{bindings.ApplUnitControlView1.hints.RowID.mandatory}"
columns="#{bindings.ApplUnitControlView1.hints.RowID.displayWidth}"
maximumLength="#{bindings.ApplUnitControlView1.hints.RowID.precision}"
shortDesc="#{bindings.ApplUnitControlView1.hints.RowID.tooltip}"
id="it8">
<f:validator binding="#{row.bindings.RowID.validator}"/>
</af:inputText>
</af:column>
</af:table>
</af:panelCollection>
</af:form>
</af:document>
</f:view>
<!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_untitled8-->
</jsp:root>
public String cb7_action() {
try {
BindingContainer bindings1 = getBindings();
DCIteratorBinding dciter = (DCIteratorBinding)bindings1.get("ApplUnitControlView1Iterator");
Row oldCcurrentRow = dciter.getCurrentRow();
BindingContainer bindings = getBindings();
OperationBinding operationBinding = bindings.getOperationBinding("CreateInsert");
Object result = operationBinding.execute();
if (!operationBinding.getErrors().isEmpty()) {
return null;
RichPopup popup = this.getP1();
RichPopup.PopupHints hints =
new RichPopup.PopupHints(); //empty hints renders dialog in center of screen
popup.show(hints);
catch (NullPointerException e)
System.out.println(" cause " + e.getCause());
System.out.println("message" + e.getLocalizedMessage());
System.out.println("stack trace" + e.getStackTrace());
return "insert";
}Edited by: ADF 7 on Feb 10, 2012 2:05 AM -
Turn Off Form Field Calculations When Printing
I am using Acrobat 9 Pro, and I will be the first to admit, I'm not all that familiar with creating functions or adding codes. Through trial and error, I have created a form that allows my clients to fill out certain form fields, and automatically totals up their entire order. If no values are entered and someone prints the document, the section that calculates the total still prints with a $0.00 value. I do have some clients who prefer to print the form and fill it out manually. My question is, is there a way to disable the form fields, so that when it prints out, the area that would normally calculate the total, would just print blank? And is it possible to add a button or check box within the PDF that would allow the form fields to be toggled on and off?
Or another option, is it possible to have the document NOT print any values that are zero or less?
Thanks!!!!You can do some of that other sutff, but if you're using one of the built-in calculation methods and just want to have the field not show a zero result, you can add the following custom validate JavaScript:
// Custom Validate script
if (+event.value === 0) event.value = ""; -
Form fields disappearing when combining PDFs
I'm having a curious issue where form fields that display properly in a one-page PDF document are disappearing when the document is combined into a larger, multi-page PDF document. The individual page (created in Acrobat Pro 8) has 12 rows of checkboxes that show up when the document is opened in Acrobat Pro 8, Pro X, or even Preview. However, after being combined into a 150-page PDF (with Acrobat Pro X), the top three rows of checkboxes have disappeared (and this occurs across all of the programs I just listed). I've tried re-doing the offending page in both Acrobat 8 and X, and replacing it within the multi-page document (again, trying both Acrobat 8 and X) and once it's combined into the larger PDF, those top three rows of checkboxes always disappear. I'm at a loss.
Any suggestions for troubleshooting this?
- Mac OS 10.6.7
- iMac 2.4ghz Core 2 Duo / 3GB RAM
- Acrobat Pro X (or 8)I'm combining them by using the "Combine Files Into a PDF" feature in Acrobat. I've done this countless times before with no issues -- this is the first time I've seen this happen.
-
Hello,
I am getting 'Thread was being aborted - Unable to evaluate expression because
the code is optimized or a native frame is on top of the call stack' error
when I use 'SPUtility.GetPrincipalsInGroup' method.
bool bReachedMaxCount = false;
SPPrincipalInfo[] _spPrincInfoColl = SPUtility.GetPrincipalsInGroup(web, groupName, Int32.MaxValue - 1, out bReachedMaxCount);
We have both SharePoint groups (SPGroup) & Active Directory groups in our site.
I am checking if logged in user has access to the group name that I am passing here as 'groupName'.
Code works without any error when I pass 'domain name' as 'groupName' e.g. (Domain\\usergroup) but the same throws error when I pass SharePoint groups (SPGroup) name.
Both type of these groups have at least 'Read' permission on site.
I have this code inside 'try-catch' block and hence I am able to catch that thread aborted error.
What could be the reason for this error? I don't get any call stack and all other properties of exception object are either null or with garbage values.
I am having SP2010 foundation, VS2012 and .Net4.5 installed on my machine.
Kindly suggest on this. Thank you.
Sagar S.I think the RunWithElevatedPrivilages is not working correctly. I believe that the new site and web objects need to be opened within elevatedprivilages to work. it looks like the way your code is working the SPsite and SPweb objects are getting opened before
the RunWithElevatedPrivilages give this a try and see if your result changes.
bool IsUserInGroup = false;
try
SPSecurity.RunWithElevatedPrivileges(() =>
Guid siteId = SPContext.Current.Site.ID;
Guid webId = SPContext.Current.Web.ID;
using (SPSite newSite = new SPSite(siteId)) {
using (SPWeb newWeb = newSite.OpenWeb(webId)){
bool bReachedMaxCount = false;
SPPrincipalInfo[] _spPrincInfoColl = SPUtility.GetPrincipalsInGroup(newWeb, "TestGroup", Int32.MaxValue - 1, out bReachedMaxCount);
if (_spPrincInfoColl.Where(a => a.LoginName == username).Count() > 0)
IsUserInGroup = true;
}//close web
}//close site
catch (Exception ex)
LogManager.LogMessage(ex.Message.ToString());
Alex -
Missing Field error when modifying user Master Record
We are using our corporate LDAP to authenticate our portal users and do not have (nor do we want) write permission to the LDAP. We are using additional attributes (ume.admin.addattrs) to hold information pertinent to the portal. We are running into a problem though when required information is missing from the LDAP user master record. For example, if the users email address is missing, when we attempt to save a user's record with the additional attributes we need, the system responds with a "Missing Field" error message and will not save the additional attribute until the LDAP record is complete. Currently the only work around to this problem is to notify the LDAP administrators and have them update the record (not a high priority for them).
Is there a way to have the portal ignore incomplete records and just save what it has?
Thanks
Ken BurdWe are using our corporate LDAP to authenticate our portal users and do not have (nor do we want) write permission to the LDAP. We are using additional attributes (ume.admin.addattrs) to hold information pertinent to the portal. We are running into a problem though when required information is missing from the LDAP user master record. For example, if the users email address is missing, when we attempt to save a user's record with the additional attributes we need, the system responds with a "Missing Field" error message and will not save the additional attribute until the LDAP record is complete. Currently the only work around to this problem is to notify the LDAP administrators and have them update the record (not a high priority for them).
Is there a way to have the portal ignore incomplete records and just save what it has?
Thanks
Ken Burd -
Get rId of Form Field boxes when printing
Hey Guys,
I created a Fillable PDF Form with Form fields using ADOBE Acrobat 9.0 Pro-Ex + LiveCycle Designer for Windows XP.
My question is, when printing the form, the form field "text boxes" always show up. Is there a way to hide the boxes and just print the form without them. (The information that was filled in will still show, just the outline of the boxes won't?)
My other question is when you create a form, is there a way to make form fields "clickable" instead of just auto-tab? Because if you mess up when filling out the form, you don't want to have to tab through the whole document just to get back to that spot. How can i fix that?
Thanks a bunch,
JosephMy fields have always been click enabled. Not sure why they would not be.
For the form field boxes, check the properties of the boxes to see if there is an option for printout. -
Is there a way for a form field to show a name when the client sees it, but have the name disappear
My client needs a PDF with fields. It's a letter. They want the areas for the header - names/addresses/company name/date, etc. to be variable, but when THEIR client looks at it, they want them to know what the field is. So they want the field labeled. But when the client then types in the field, they want that label to disappear.
This one has me stumped! Thanks!In a text field, use Options > Default value. The user will have to delete what you write there when entering new text, or you'll get both.
-
Text in form field disappears when I move to next field
I have a PDF form for doing estimates for my business. I e-mailed it to myself and open it up on iPad. Then I selected open in Adobe.
I can enter data in any of the fields just fine but when I move to the next field the data I previously entered disappears unless I go back to that field to edit.
I tried e-mailing a document to myself and when I opened it up on my laptop computer the data fields are empty regardless of whether I highlight that field.
Can anybody help me out with this problem?
Thank you, Bob Kroth
[email protected]Hi Pat,
Well I'm not sure what doc you were looking at but here is a similar pdf.
I have both Adobe and Scan soft PDF software. If you mouse over the area
where the address would be typed in and click on that area the text that is
there will appear. When you click to new field text disapears. I typed in a
price for mowing and when you click on that field you can see the price. I
have also tried this on Adobe for iPhone and have the same problem.
Sorry if I'm not explaining this clearly.
Bob 612 889-5720 -
Making a form field required when another field is selected
I have a contact form with the usual fields required (name, address, city, etc.). I'm adding a Country pull-down list to the form, which will default to the US being selected. Since a "State" field is not relevant for anyone filling out the form from another country, I'd like to make the State field required only if the country selected is United States, and not required for any other country. Is there a way to do this?
Thanks,
R-CoWhat you need is to be able to create a required textfield when the first textfield shows USA and destroy the required field when another country is selected.
The following may help to understand create and destroy
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Deleting and rebuilding validations</title>
<link href="http://labs.adobe.com/technologies/spry/widgets/textfieldvalidation/SpryValidationTextFiel d.css" rel="stylesheet">
</head>
<body>
<form id="form1" method="post" action="#">
<p>
<input type="radio" name="radio" id="Married" value="Married" onclick="val(this);">
<label for="Married">Married</label>
</p>
<p>
<input type="radio" name="radio" id="Defacto" value="Defacto" onclick="val(this);">
<label for="Defacto">Defacto</label>
</p>
<p>
<input type="radio" name="radio" id="Single" value="Single" onclick="val(this);">
<label for="radio">Single</label>
</p>
<hr>
<span id="sprytextfield1">
<label for="f_married">Married</label>
<input name="married" id="f_married" type="text" value="">
<span class="textfieldRequiredMsg">A value is required.</span>
</span>
<span id="sprytextfield2">
<label for="f_defacto">Defacto</label>
<input name="defacto" id="f_defacto" type="text" value="">
<span class="textfieldRequiredMsg">A value is required.</span>
</span>
<span id="sprytextfield3">
<label for="f_single">Single</label>
<input name="single" id="f_single" type="text" value="">
<span class="textfieldRequiredMsg">A value is required.</span>
</span>
<hr>
<input type="submit" value="Submit" />
</form>
<script src="http://labs.adobe.com/technologies/spry/includes_minified/SpryValidationTextField.js"></script>
<script>
var sprytextfield1,
sprytextfield2,
sprytextfield3;
// build validations and delete / destroy them
function val(e){
// get the value
value = e.value;
// see what radion button we have
if(value == "Married"){
// if there inst a validaton build one
if(!sprytextfield1){
sprytextfield1 = new Spry.Widget.ValidationTextField("sprytextfield1");
// if there is a validaiton in sprytextfield destory it, and clear the variable
if(sprytextfield2 && sprytextfield2.destroy){
sprytextfield2.resetClasses();
sprytextfield2.destroy();
sprytextfield2 = null;
// same as the rest
if(sprytextfield3 && sprytextfield3.destroy){
sprytextfield3.resetClasses();
sprytextfield3.destroy();
sprytextfield3 = null;
} else if(value == 'Defacto'){
if(!sprytextfield2){
sprytextfield2 = new Spry.Widget.ValidationTextField("sprytextfield2");
if(sprytextfield1 && sprytextfield1.destroy){
sprytextfield1.resetClasses();
sprytextfield1.destroy();
sprytextfield1 = null;
if(sprytextfield3 && sprytextfield3.destroy){
sprytextfield3.resetClasses();
sprytextfield3.destroy();
sprytextfield3 = null;
} else if(value == 'Single'){
if(!sprytextfield3){
sprytextfield3 = new Spry.Widget.ValidationTextField("sprytextfield3");
if(sprytextfield1 && sprytextfield1.destroy){
sprytextfield1.resetClasses();
sprytextfield1.destroy();
sprytextfield1 = null;
if(sprytextfield2 && sprytextfield2.destroy){
sprytextfield2.resetClasses();
sprytextfield2.destroy();
sprytextfield2 = null;
// proceed with the rest as normal
return true;
</script>
</body>
</html> -
Compiled and trying to deploy a form - an error when calling the form
Hi!
I used to deal with Forms 6i and I'm quite new to 10g.
Is it enough to just replace an .fmx file on the server?
We have a software product written on Forms 10g which is running on our server.
I found where working .fmx files are located on the server.
I also found which seems to be the source files.
My actions:
1) Selected one of the forms and compiled it in Bulder 10g successfully.
2) Replaced an .fmx file with one which I had comiled.
3) In user interface, press the button which calls my form, but nothing happens. The form is not created. No error messages.
4) Put the original .fmx back - and everyting works: after pressing the button the form starts.
What's wrong? Improper way of compilation or deployment?
Any suggestion would be appreciated.
Thanking in advance,
RomanRoman Churakov wrote:
Thank you, Christian!
You are right!
According to my last test, when I try to call the form directly from the url (via parameter form=myform.fmx), I get the following:
1) With the orginal myform.fmx, the form starts
2) With the form compiled by me, I get error: "Cannot read form myform.fmx"
Though the file names are identical, the file compiled on windows doesn't go.
P. S.
Nevertheless, that's weird for me: I supposed that since Forms 10g is based on Java, the compilation must be platform-independent.
Edited by: Roman Churakov on 20.01.2012 1:58I think you have just a problem with upper/lowercase.
.) ensure your fmx is exactly myform.fmx
I am not sure but I think you get this message also if there is a wrong attached-library-name in the source.
So if its still not working convert the fmb to text (file->convert...), check if the libraries are attached correctly (case sensitive on UX/LX) the libs are visible in the first lines, check if some libs are attached multiple times, correct that stuff, and convert back from text to fmb.
Hope that helps!
Maybe you are looking for
-
Hi! When I enter fix values into a domain, it is appearing automatically through the data element in an element of a view (like a dropdown by key). That's nice, it is working perfectly. However if I don't use fix values in the domain, but I use a val
-
ScreenSaver coming on when in Full Screen Mode
Hi Guys, My father-in-Law got the Quicktime pro 7 for windows, I still haven't been able to get him to buy a mac... but that's another story. When we installed the software on his laptop, everything works fine, but when watching an .mp4 file, we noti
-
Difference between Business Partner and Customer in ISU?
Is there any difference between business partner and customer in ISU? if yes then wht?
-
hi experts..... i am new to jms scenario can any one give me the guidence of designing part in integration repository with sceern shots possible? thank you so much in advance
-
MaxL with DATAEXPORT and passed parameters
Have a MaxL script that is passed four parameters. Within the MaxL script I am executing a DATAEXPORT calculation, not a calc script. I want to use some of the parameters as part of the output filename. I have tried various combintaion of single quot