You are viewing limited content. For full access, please sign in.

Question

Question

Save to Default Folder - error when using required fields

Version 10 Laserfiche
Updated November 7, 2018
asked on November 7, 2018

Hi All,

 

I've done some testing when using and altering the behaviour of the "Save to Default Folder" button in Outlook.

 

 

You can change the location this saves in the user attributes:-

 

 

However if you have a template that has required fields, then it shows an error message before you get to the metadata part of the import:-

 

 

You can click OK and proceed normally, but can the pop up/error message be removed?

 

Cheers!

0 0

Replies

replied on November 7, 2018

I would add some default value just to workaround this problem. (To the template)

"NULL" or something in the required fields - don't know if you can do that!

Cheers!

0 0
View 7 previous replies
replied on November 7, 2018

Hmmmm. That would fix the issue, but kind of then defeats the object of having required fields?...frown

0 0
replied on November 7, 2018 • Show version history

Unless you use your assign field values tool in workflow to remove the existing values? (Post import)

 

0 0
replied on November 7, 2018

Yeah I guess, but the idea is to have the user complete the required field on import. Good thinking though!

0 0
replied on November 7, 2018

Oh I see. I didn't get that part.

Explain to me again please, they are saving from Outlook in to LF? 

Then it auto imports and this is where the error pops up?

0 0
replied on November 7, 2018 • Show version history

Yes that's right, this seems to me like it's a bug.

0 0
replied on November 7, 2018 • Show version history

Ok so its pre or post import that you want them to enter the metadata? (Sorry just trying to understand, I have a similar process)

0 0
replied on November 7, 2018

Pre-Import.

0 0
replied on November 7, 2018

It's weird, if they are typing in to the required fields this shouldn't be occurring.

 

0 0
replied on November 7, 2018

This is the issue, this error pops up before you get to metadata entry wink

0 0
replied on November 7, 2018

What are you suppose to type in the required field? I still think you should give the required field some kind of arbitrary constraint and a default value on top of that.

So that it imports at least, when it is in LF you can do with it whatever you want you know.

I'd still give it an arbitrary default value and if the entry has that default value once the end user saves and has completed all the metadata just have a Workflow check the two fields (it looks like two since the error comes up twice).

I mean, other than that I got nothing!

Good luck Chris.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...