Question

Forms: Adding fields to Repository Task does not allow upload to repo

Forms

Updated April 15, 2021

asked on April 14, 2021 • Show version history

Greetings all,

I can successfully upload a form submission to my repository without metadata fields assigned.

The issue is that I need to be able to upload with metadata fields.

In the process diagram, whenever I add a single field in Configure Fields inside the Save to Repository Service Task and test the process, the repo service task stage gets suspended with no message. If i go back to the process diagram and remove the single field that i added, the suspended processes resume and successfully upload without any fields for metadata.

I am sure that this is probably a simple user error or misunderstanding on my part but any help is appreciated.

0 0

Answer

SELECTED ANSWER

replied on April 15, 2021 • Show version history

Issue 1:
- Some fields had patterns / regular expressions set (on either the Lf Repo Client or Lf Admin Console) that I wasn't aware of and this was rejecting any repo upload attempts.
Solution 1:
- Find out field restraints and apply field validation to meet said restraints.

Issue 2:
- Other fields, though visible on the repo service task, were restricted to specific repo profiles. The repo profile that I was using in forms was not on the list of authorized profiles to use said field.
Solution 2:
- Go onto the Laserfiche Administration Console > Metadata Management and add the repo profile and edit permission you wish to use to the field desired.

Closing remarks: It would be nice to know if there was a way to view a field's restrictions when selecting fields to add to the Save to Repo Service Task.

2 0

Replies

replied on April 14, 2021

Hi Fernando-

The Event Viewer on the Forms server should give you some information about what's going on, which you can also get to from the Monitor tab in Forms.

Common reasons for this would be putting an invalid value into the field--for example, if there's a constraint to limit the type of input. Or if you're trying to set a single field with a template, but there's another field on the template that's required.

2 0

replied on April 15, 2021 • Show version history

Hello Pieter,

Thank you for responding.

I am only adding individual fields and not using templates.

You're right, the field seemed to have some type of regular expression / pattern applied that I couldn't see.

I checked the Repository Admin Console to view information that might be restricting on said field and there didn't seem to be any. I just changed my input to match what is generally used for the field (ID) and it worked.

However, when I tried using another field (Name) that shouldn't really have a pattern, the issue returned.

Bad field value ('Name'): Access denied. [9013]

Is there anyway to know a field's restraints before I attempt to add them to the repo task?

Update: I noticed that the profile used in Forms to upload to the repo was not on the list of authorized users for the Name field in the Repo Admin Console. The profile now has access to the Name field but the exact same error and message persists.

0 0

You are not allowed to follow up in this post.

Question

Question

Forms: Adding fields to Repository Task does not allow upload to repo

Answer

Replies

Sign in to reply to this post.