cancel
Showing results for 
Search instead for 
Did you mean: 

Addition of record in Tuple/Look Up + Define default no of records

Former Member
0 Kudos

Hi,

1)Is it possible to add record automatically in look up or tuple based on some logic/condition (Not via import server), in other words, can we add record automatically based on checking condition via validation or assignment?

2) Can we define default number of records in look up or tuple?

Thanks,

Priya

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member208981
Contributor
0 Kudos

Hi,

1)Is it possible to add record automatically in look up or tuple based on some logic/condition (Not via import server), in other words, can we add record automatically based on checking condition via validation or assignment?

2) Can we define default number of records in look up or tuple?

Hi Priya,

1. You can assign a validation /assignment in Data Manager and execute them as part of a workflow on add/update of a record. But these assignments / validations will be predefined. It will not be like you can do via Import Manager.

2. I am not aware of any method that limits the number of records.

Thanks,

Priti

Former Member
0 Kudos

Hi Priti,

to answer to your point 1) Any assignment or validation runs on record, what i want it, to create/add record automatically. How is this possible? Can you give some example ?

Former Member
0 Kudos

Hi Priya

Both the requirements are not possible.

Adding a new record in repository or table is purely a business need based scenario and automating this will not make sense.

For the new records to be created either they need to be created by Users(MDM GUis, Portal GUis, web etc) or can be automatically crated from interfaces using MDIS.

best regards

Ravi

former_member208981
Contributor
0 Kudos

Hi Priya,

Sory.. I guess I misunderstood your question.

Can you please explain the requirement you have exactly?

Did you mean you dont want use MDIS to automatically import data? If so, I agree with Ravi's reply.

Any Assignment/ validation will be on the record that already exists in Data Manager.

The only way to control records that can be imported based on the matching field.

Thanks,

Priti

Former Member
0 Kudos

Hi Ravi,

Thanks, I am not agree that automatic addition will not make any sense. It depends on business needs and i can see the logical requirement from business where they want to create record based on checking condition, it is a conditional record creation and not just dummy record. In worst case, is it possible to define default number of records any table holds? may be from back end/at DB level, We are using oracle. Any thoughts around this will be helpful

Former Member
0 Kudos

Hi Priya,

1)Is it possible to add record automatically in look up or tuple based on some logic/condition (Not via import server), in other words, can we add record automatically based on checking condition via validation or assignment?

You can do it using MDM workflow where you need to use Start Step (Checkout) Branch Step (for validation Purpose like Product ID field length = 10) if this validation TRUE pass it to STOP(Check In) else pass it to STOP2 (Rollback) will result in not record committed(created) into MDM. You can define more than one validation in Branch step and can therefore add record automatically using MDM Workflow which fulfill this conditions(validations) and which does not fulfill will be rolled back.

You will select this MDM Workflow using Configuration Options and then will save this in Import Map. So every time when record comes through Import Manager/ImportServer it will go into this workflow.

Start(Checkout)>(Branch based on conditions(Validations))>TRUE(Stop1(Checkin)) Records get created

-


>FALSE(Stop2(Rollback)) Records will not create into MDM

Obviously, you have to use either MDM Workflow using MDM Import Manager/Import Server, Data Manager directly or through Portal.

2) Can we define default number of records in look up or tuple?

As per my understanding this is not Possible directly but can be achieved using workaround. e.g. you have Countries lookup table and you want to set Countries name to 200. For this you need to create a new field of TYPE AUTOID and need to write Validation AUTOID<=200 and need to set Automatic Execution Property of Validation = Error.

Regarding Tuple it is altogether different concept and can be either Single Valued Tuple or Multivalued tuple. It is not like lookup table which contains values as we can see the lookup values of lookup table by selecting lookup table as current table in Record Mode of MDM Data Manager.

Regards,

Mandeep Saini

Former Member
0 Kudos

Hi Priya

As explained by Mandeep you can use checkout step as part of Start step in the workflow and only after the record is approved/validated it will be Checked in/created otherwise rolled back which means no record will be created.

For the 2nd requirement you can define a field in the table as AUTOID and write a validation AutoID< max no of records to which entries need to be restricted for that table with execution as Error.

But this will not take care of the entries deleted from the table. For each deletion one Auto ID is lost, so say if you want max entries in table to 200 and also delete 5 records that the system will not allow you to create 196th record.

hope this helps.

Ravi