Hi Ziyan,

We did the upgrade over the weekend, and it does work now with the new forms designer for the most part, but I'm having two issues.

1. FormsLinkURL issue I added the below text to the end of my forms link for my custom tab, and everything auto fills except the "_DatePOAReceived" field. If I manually type in values for the variables with my link into the web browser, it works, but if I try to use the variables as shown below, it does not work. I'm not sure what is wrong.

?_POAEntryID={id}&_DatePOAReceived=[Orig Date]&_MemberName=[Full Name]&_AcctNo=[AcctNo]

2. Read only issue If a field is set to read only on the form, it won't pass the variables over to the fields. Is this a known bug?

Thanks.

Hi Jessica,

Glad to know it works for the most part.

For mentioned read-only issue, this is expected behavior to not populate read-only fields with values in URL. The reason is that value of read-only fields are determined by backend for data security, so the value filled in frontend will not be passed to backend at all. 

As alternative, you can populate the read-only field with default value/formula/lookup rule, which will be regarded by backend.

For the first issue, I'm still unsure about the situation. Where does the variable [Orig Date] come from? What is the format of this variable?

Hi Ziyan, I figured out that the date issue was because I was using MM/DD/YYYY format for the field and it only seems to work as a YYYY-MM-DD format for some reason. (I'm assuming it has something to do with the metadata field setup, even though our data shows as MM/DD/YYYY when viewing the file metadata).

I don't think I can do a backend lookup on the data I need to populate in the read only fields, so I just didn't mark them read only. This isn't our preferred method though. I need entry ID to populate and I was trying to make that read only, and really, I wanted Creation Date for the other read only field, but since that field won't pass in the URL, I used our metadata field [ORIG DATE], which will be set to the creation date for the specific files in question.

Thanks.

Hi Jessica,

One workaround for both issues is to add hidden helper editable field, then use it as formula of target field:

For example, for the first issue, add a helper editable field with date format YYYY-MM-DD (if it is the only date format when passed from Web Client), and populate it with URL. Then use it as formula of the target date field which has preferred format MM/DD/YYYY. 

To hide the helper field, simply setup field rule to always hide it.