Comments on: Who needs Group Populator when you have Multivalue tables?

By: Carol

Carol — Mon, 13 Dec 2010 19:50:42 +0000

Yep still here. You can definitely use this for exports, and while I’ve only ever done it with SQL I gather it works just the same for Oracle.

By: Kal

Kal — Mon, 13 Dec 2010 19:46:26 +0000

I realize this is an old one, I was just wondering(hope you are still listening), can you do that with export meaning, syncing groups + members to tables in Oracle (or SQL)?

How would the configuration change in this case?

By: Sundar

Sundar — Tue, 13 Jul 2010 09:18:50 +0000

Really a very good link..it solved my problem

By: Carol

Carol — Thu, 23 Apr 2009 18:39:22 +0000

JB,
It certainly is possible to export to a table with an identity column – you just leave the value blank and let SQL populate it – but I expect there would be a problem if that column was also the key. I think when I’ve done this in the past I’ve used something else for the key that I can populate from MIIS, and then use another column for the self-seeded identity.
Sorry I’m a bit vague – haven’t done it in a while – but I see you’ve posted on the forum as well so you’re bound to get some good answers there.

By: jbwilliams11

jbwilliams11 — Thu, 23 Apr 2009 17:18:40 +0000

I am using MIIS 2003 (ILM 2007) and I am having a problem provisioning a record to a SQL 2005 database table. The database table has about 18 attributes with 1 of them being a PK (call this attrib01), which is an autgenerated number. This specific MA (call it MA01) has all the attributes in the table defined in the attribute flow to export with the exception of the PK field (b/c it is read only in the CS meaning it is the Anchor Attribute). When I run my Full Imports/Full Synchs (all MAs) the proper MAs (in this case MA01) receive provision/export notifications. During the Export run MA01 I get an exception from my provision DLL that attrib01 is not present. I tried setting attrib01 to a generic value (knowing it is autgenerated) in the provisioning DLL and I still get an exception but it is different stating that attrib01 is read only. Bottom line is I cannot insert a new record in the db table because of attrib01.

I am now looking into an Extensible MA but have never created one before.

I would appreciate any ideas on how to get by this?

By: clifton.leonard

clifton.leonard — Wed, 05 Nov 2008 17:07:31 +0000

Sorry Carol, I saw someone had referred to Rich, and thought that was you. I figured out my problem, as I wasn’t importing the user objects into the MV through the same MA that I was exporting the groups through. I thought since I was doing it through another MA from AD, and the MV group references to user objects were working, that it should have exported it automatically. However, as soon as I imported/joined these users objects in on the group MA from AD, it worked like a champ. Thanks again for this post, and it was very helpful!…

By: Carol

Carol — Fri, 31 Oct 2008 10:06:21 +0000

Clifton,

Rich? Who’s Rich? My name is Carol, though I will answer to Miss MIIS if you like that sort of thing

Anyway, no members exporting. Things to check:
- do you have both user and group objects selected in the ADMA?
- can you see the group members in the connector space?
- if you export to a log file are the members in the file?

By: clifton.leonard

clifton.leonard — Fri, 31 Oct 2008 01:58:34 +0000

Rich,

Thank you sooo much for this post. Everything was perfect for recreating a similar situation in my environment. With a minor difference (Oracle instead of SQL), I was still able to get most of it working with your detailed instructions, except for one minor problem that I was hoping you might be able to help with…
I have everything sync’ed into the MV, with my user objects as reference values, however, it won’t export into AD. The groups get created, permissions are set correctly, but no members in the groups, and no errors. I am exporting member (group) directly to member (group), and the user objects already exist in the MV…I even tried sync’ing the user objects, thinking this would export the membership…
I feel like I’m missing something important here (ie., rules extension, etc), and couldn’t find any more instructions on your posting for creating the AD MA…
In actuallity, this is the ONLY posting of a good Group Populator in MIIS, without using Group Populator, so thanks again for everything!…

By: Carol

Carol — Tue, 10 Jun 2008 16:08:20 +0000

I think what you really have here is a single valued table in a slightly unusual format. So I think you will need another MA and you will have to make the anchor a combination of the user ID and the field ID.

By: jashaffner

jashaffner — Tue, 10 Jun 2008 14:06:11 +0000

It is because the app allows end users to add custom fields on the fly, hence, the purpose of the third table, storing the field names along with other attributes like maxlength, datatype, etc.

I would like to clarify that while we have a table storing custom fields (#3), we are storing a single value for each field for each user in table #1.

Is it still doable with the usage of multivalue table approach to keep table #1in sync with MV?

Thanks a bunch!