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

Question

Question

Is it possible to edit a Dynamic Fields?

Updated December 4, 2013
asked on November 27, 2013

I have an external table containing the following data:

Customer ID

Name

Invoce Number

Product

 

When someone import a document into Laserfiche, it is necessary to put only the Customer ID that the rest of the fields are automatically populated as they are Dynamics Fields.
But if we receive a new invoice could not fill the field with this new data. We have to edit the External Table.
So, is there any way to populate a Dynamic Fields without the need to edit the external table?

 

 

0 0

Answer

APPROVED ANSWER
replied on November 27, 2013

Hi Danilo-

 

To expand on Ken's answer a little, the basic point is no, there is no way to edit the tables used for dynamic fields directly from the Laserfiche UI.

 

However, manually adding the invoice number to a table is not very efficient and therefore not recommended. Instead, let the software do this for you. Both Quick Fields and Workflow can update a database, with Workflow being the easiest option.

 

One idea: have a field that accepts invoice numbers for new invoices. Then, Workflow can take that value, put it in the table, and set the dynamic field to that value.

 

Of course, another option is to integrate Laserfiche with your accounting system so that the invoice numbers get in there earlier.

0 0

Replies

replied on December 4, 2013

If the dynamic records are only used by laserfiche and do not  "live" in another application I like to create a parallel template that is NOT dynamic, like NEW customer template. The template has the same exact fields so that you can allow them to fill in the fields manually.

 

I then run a workflow that checks to see if it's in the list already, and if not add that information to the list. 

 

It gets really complex if there are a lot of dynamic child fields but if it's only a few it's not too hard. 

 

 

1 0
replied on November 27, 2013 • Show version history

The following recommendations are if you were trying to make an automated system. They are not completely thought out solutions, but I do hope they point you in the right direction. 

 

I recommend the use of secondary fields and workflow to help you maintain the database on the fly as opposed to manually editing it. 

 

Alternative solutions include using a form to upload the document and use workflow to update the DB and then apply the metadata. Assuming you have a Forms License 

0 0
replied on November 29, 2013 • Show version history

Hi Danilo,

 

Pieter make a good point about integration.

 

However, in truth there's not enough information in your query to give you a worthwhile answer. There are a number of other options (like using Laserfiche templates to update the database via the workflow and using templates to create an SQL view, no additional tables required) but here is a one scenario we've use:

 

A customer insists on keeping everything in Laserfiche, such as all customer contact records, too. One of them creates black document using the template with all the customer details. Another creates a customer folder with the template contacting all the details.

 

When a new record is added to LF, it's given a different template with similar fields. The workflow checks the customer number given to the new document against the customer contact records and when there's a match, copies the metadata.

 

-Ben

 

0 0
replied on November 29, 2013

Hi Danilo,

 

Pieter make a good point about integration.

 

However, in truth there's not enough information in your query to give you a worthwhile answer. There are a number of other options (like using Laserfiche templates to update the database via the workflow) but here is a one scenario we've use:

 

A customer insists on keeping everything in Laserfiche, such as all customer contact records, too. One of them creates black document using the template with all the customer details. Another creates a customer folder with the template contacting all the details.

 

When a new record is added to LF, it's given a different template with similar fields. The workflow checks the customer number given to the new document against the customer contact records and when there's a match, copies the metadata.

 

-Ben

 

replied on November 29, 2013

Hi Danilo,

 

Pieter make a good point about integration.

 

However, in truth there's not enough information in your query to give you a worthwhile answer. There are a number of other options (like using Laserfiche templates to update the database via the workflow) but here is a one scenario we've use:

 

A customer insists on keeping everything in Laserfiche, such as all customer contact records, too. One of them creates black document using the template with all the customer details. Another creates a customer folder with the template contacting all the details.

 

When a new record is added to LF, it's given a different template with similar fields. The workflow checks the customer number given to the new document against the customer contact records and when there's a match, copies the metadata.

 

-Ben

 

replied on November 29, 2013

Hi Danilo,

 

Pieter make a good point about integration.

 

However, in truth there's not enough information in your query to give you a worthwhile answer. There are a number of other options (like using Laserfiche templates to update the database via the workflow) but here is a one scenario we've use:

 

A customer insists on keeping everything in Laserfiche, such as all customer contact records, too. One of them creates black document using the template with all the customer details. Another creates a customer folder with the template contacting all the details.

 

When a new record is added to LF, it's given a different template with similar fields. The workflow checks the customer number given to the new document against the customer contact records and when there's a match, copies the metadata.

 

-Ben

 

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...