Home » discuss » Public forums » iMIS Community

pre-poplation of multi-instance customer table/window

Posted November 7th, 2011 by francine_kruger
|

Hi

New to iMIS. I am trying to figure out if it is possible to prepopulate a finite number of rows/instances in a multi-instance table/window when a  customer/member is first created - and then also need to be able to stop them from adding or removing any rows.

For example, we need to capture a Primary Employer, Secondary Employer and Third Employer. There must only and always be one of each.

I am restricted to the way the system was set up on implementation where by the user is required to create the three rows manually. Subsequen extracts requrie there to be the three rows and the obvious rules apply in that the Primary must first be populated - there should be be a secondary or third without a primary etc.

It would be ideal to have a list that the user can use an up/down arrow to change the order of the employers - but I think I am correct in saying that iMIS does not support this.

Therefore, I am wanting to see if I can prepopulate the primary, secondary and third rows with their type ("Primary", Secondary", "Third") and then create the table rows regardless of whether or not the user adds the additional data (i.e. name). I will need to either protect the Type, or check that they have 1 of each type afterwards, and also add the validation to check that the rows were populated correctly (primary before secondary etc).

OR am I going to have to redesign the underlying table (thereby needing to do a data conversion) to store all three employers on a single row and redesign the window (and extracts etc) to match? I think this would make the validation process much easier.

Just wanting to check my options.

Many Thanks

‹ Word merge letters - Search parameter default sourceThe Control ID 'LoginUpdatePanel' requires a scriptmanager on the page error ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

On the right track

On November 8th, 2011 Bruce Wilson says:

Hi,

For a new user of iMIS, you seem to have a good sense of how things fit together.

Your idea for adding three and preventing more is a good one.  Unfortunately, iMIS doesn't provide much support for this.  Some suggestions:

  • It is possible (and custom, but not too terribly so) to automatically add the three rows to a MI UDT using SQL.  Once you get there, iMIS doesn't provide any way to prevent them from adding or deleting rows without also preventing edits.
  • Create the table with three sets of employer information, but set each group on its own tab so all three tabs look the same.  This will feel more like a multi-instance table than putting them all on one tab.
  • If you're ready to move into iParts, we have a Multi-Instance Editor iPart which can allow edits without also permitting adds and deletes, as well as many other useful features (required fields, calculated fields, ID lookups).  To use the iPart, you would have to edit records using the staff web view.

For more information about our iParts or a demo, please email Brenda Barnhart (brenda.barnhart@mcgladrey.com).

--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.

login or register to post comments

customer creation calling sql

On November 22nd, 2011 francine_kruger says:

Thanks for the prompt response

I have been trying to find (unsuccessfully) where in the iMIS configuration I can define a call to the required sql stmts - I need to create the 3 records in the table when the customer is first being created, even if they do not go to the employer tab - where in iMIS do you set this up?

Thanks

Francine

login or register to post comments

That's why it's custom.

On November 22nd, 2011 Bruce Wilson says:

There is no place in iMIS where you can define this.  That's why it's custom.

One way to make this happen is a SQL trigger.  Triggers can be tricky to create and administer.

Another way is to create a stored procedure and run it on a regular and very short schedule, say, once a minute.  This is preferred over a trigger because it is less likely to cause problems with iMIS.  For most business requirements, "within a minute" is fast enough.
--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.

login or register to post comments