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

Question

Question

Feature Request - disable Lookup Rules

asked on January 11, 2016

Scenario One:

I have just developed a set of forms on a 'dev' server with a major bunch of Lookup Rules in each form.  These lookups are lost when the forms are downloaded and uploaded to a customer's production server.  Even if the databases already exist, they can't be used until the Form Process is added to the Data Source.  By this time the Lookup Rules are already lost.

It would be beneficial if the Upload could import the Lookup Rules intact, but disable them.  A disable/enable button could be used to enable them once the Data Sources were in place.  Otherwise all Lookup Rules have to be re-written.

 

Scenario Two:

There are times during form development when changes to databases occur or where you wish to temporarily disable a Lookup Rule.  It would be beneficial if the Lookup Rules could be disabled/enabled via a new button. 

 

6 0

Answer

SELECTED ANSWER
replied on January 12, 2016

I have the same complaint about importing a process. Just so that you know, you can edit the XML file to import the business process with the lookups intact so long as you take these steps:

  1. Add the data source first (make sure all the tables/views/procedures you need are in place and named exactly what they should be based on your Dev version).
  2. Edit the business process XML file in your favorite text editor. Search for all <externaldatabase> nodes, and then update the server, database, and user information nested below each one. Make sure the server, database, and user match exactly the data source you added in 1.
  3. Import your modified XML file.

 

I like your concept for how to handle the lookup rules with an enable/disable toggle. That would be a good way to handle them if they implement this kind of feature.

4 0
replied on January 12, 2016

Thanks Scott.  Not too difficult once you know where to look.

0 1

Replies

replied on January 12, 2016

Enable/disable toggling would be great with field rules too, not to mention process modeler activities. Workflow has that feature and so should Forms in my opinion.

2 0
replied on January 12, 2016

Good idea Ege.  I like your idea about field rules.

0 0
replied on July 24, 2017

I'm trying to upload an XML file after editing, as described above, to try to keep the lookup rules intact. However, I get this error when trying to upload:

Reading the XML file returned error - Duplicate attribute found. Both 'i:nil' and 'i:nil' are from the namespace 'http://www.w3.org/2001/XMLSchema-instance'. Line 1, position 184.. [LFF317-UnableToReadXml]

How can I fix this?

You are not allowed to follow up in this post.

Sign in to reply to this post.