MDM limitations?

I would like to
1) What is the maximum number of fields that can be created in main table?
2) What is the maximum number of fields that can be created in qualified table?

Hi Subin,
1) What is the maximum number of fields that can be created in main table?
There is no such thing as maximum limit of fields on Main Table.
It all depends on the following:
1.Business requirement - The data model heavily depends on Business requirement.
e.g If you want to maintain Material master data the number of fields can be more as compared to Customer master data.
2.Customer requirement - This is also a major driver in deciding number of fields.
e.g If Customer wants to have most of data in MDM he can have a repository loaded with fields whereas if MDM maintains only global data then MDM will be having fewer fields.
3.Landscape - Data Model and number of fields are also influenced by the type and nature of systems talking to MDM.
e.g One might require few remote system specific fields etc.
4.Workarounds and Design - It is up to the designer of the Data Model to optimize the number of fields in the repository.
Many a times one has to put in dummy or extra fields just to achieve some requirement,which normally is not achievable in normal scenario.
5.Future Enhancements - Many customers wish to create extra fields so that there future requirements are met.
This is also business driven.
6.Data Model - It is upto Consultants to optimize this and make a healthy scalable Data Model with optimum number of fields.
Choice of table and data flow governs this.
2) What is the maximum number of fields that can be created in qualified table?
Again here there is no fixed rule on this.But main deciding factor here is the fields in a Qualified table should be logically connected.
Also here one has to consider if for One line item in main table are you getting multiple line items,if yes then one can put this in Qualified table or Tuples.
e.g If field belongs to MARA table it should be in Main table and if it belongs at plant level it should be at Qualified or Tuple level.
As a healthy practice all Lookups should not have more than 30% of data content.
Hope this helps.
Thanks,
Ravi

Similar Messages

MDM Limitation Maximum number of records ?

Hello,
we have requirement to implement SAP MDM. Customer has 20 million entries for its customer data. Can MDM support this? I heard maximum MDM can handle only 6 millions entries, above that it cannot work.
Please confirm.

Hi Dony,
I think you need to do sizing as per number of records.
https://websmp109.sap-ag.de/~sapidb/011000358700001921872008E
You need SAP Service Market place SUID and Password for open above link (MDM sizing guide).
I think you can check with SAP if you still have doubts regarding the number of records.
Please find similar thread as given below:
Does MDM 7.1 have any limitations re: number of records per repository?
Hope this helps..
Regards,
Mandeep Saini

Limitations in SAP MDM!!

Dear Experts,
Does anyone know about Limitations in SAP MDM!!
Could you please let me know in detail??
Kind Regards
Eva M

Hi Eva,
What type of limitations are you refering to.
One of the major limitations that we have faced in our implementation is if the file size is too big, may be cause of the number of records and the fields mapped out it gets very difficult to manually syndicate the file. If you have any other specific issues could help on that.
In addition some general issue are
Sharing of Lookup tables (e.g. country) across repositories not supported. Linking of objects residing in 2 repositories is not supported with SAP NetWeaverMDM 5.5, natively.Workarounds via the integration into SAP NetWeaver Portal
Use of u201Ceventing technologyu201D mapping of key fields and match of respective values Not sufficient for each and every use case
There is no Migration options. One needs to manually make the changes right from development through to the production environment.
there are lots of limitations on Qualified Lookups in MDM 5.5 and also in MDM 7.1....
1) Can't write Assignments...
2) Failed validation won't specify which qualified link has failed.
3) Compare records won't show link wise comparison of qualified links.
4) Can't start qualified link level workflows.
5) Role level constraints not applicable for Qualified lookup and tables referencing from QL directly or indirectly.
6) Qualified link level check-in check-out operations are not possible.
7) Qualified link level unique constraints are not possible (this becomes pain if links get duplicated by mistake)
8) Duplication of QL link is not allowed in data manager (for copying Qualifier values in new Qualified link).
9) Tuple is replacement for qualified lookup, but its more restrictive than QL (validation are not allowed on multivalued tuple).
One Major limitation that was there in 5.5 was we could only maintain a single Maintable. 7.1 solves that problem.
The following link gives some good examples:
http://www.it-director.com/technology/data_mgmt/content.php?cid=10837
Do let me know in case you need more help or if i was able to help answer your question

Limitations of SRM-MDM by NOT using Windows + SQL Server

Hi all,
our consultants told us, that there are some sort of "limitations" if we install SRM-MDM other platforms than Windows + SQL Server; as example we were told, that e. g. the upload of BMECat files is not possible.
Is that true? If yes, where can I get a full list of "platform dependent" limitations?
We don't want to go for Windows nor SQL-Server if possible at all...
Thanx!
Regards,
Markus

Hi
Incase you are using SRM 6.0, then ->
SAP SRM 6.0 is a big step forward for SRM: SRM 6.0 is the first SAP software to rely on the new user interface technology WebDynpro and the Web Application Server, rather than the previous ITS. It is also based on the completely new business rule framework (BRF) to define approval workflows. These changes are intended to improve usability and simplify workflow administration / customization, leading to better acceptance and lower TCO for our customers. However, the move to these new technologies is also a complex change and as a result, the product has experienced delays.
With our most recent development milestone - service pack 2 in mid-July 2007 - we have made lots of progress towards completion; however, we estimated that the product was still not yet ready for Ramp-Up. As a result, we decided to release the product only in beta shipment and to a very limited set of customers (14 in total) who are being closely monitored by our development organization. Seven of these customers are actually planning to go live on the current beta shipment.
Based on the progress made so far with Service Pack 2, we feel that we should be able to start the official Ramp-Up process on December 10th, 2007 - the target ship date for Service Pack 03. By that time, we should already have 3+ live customers, so new customers starting their projects will benefit from the experiences acquired from previous implementations.
Time plan and Recommendations
1. Ideally, we recommend that new and upgrade SRM customers wait for the start of Ramp-Up for SRM 6.0 SP03 (Dec 10th, 2007) rather than starting a project with the previous release SRM 5.0. SRM 6.0 offers many benefits compared to SRM 5.0 and should be easier to use + maintain. An Online scoping questionnaire will be available from mid October in the SAP Service Marketplace as usual.
2. The number of Beta shipment customers is strictly limited and therefore we do not intend to ship Service Pack 2 to any additional customers besides the 14 customers currently in Beta.
3. Implementation partners can request a demo license of the current support package 2 in the partner portal. They can set up their sandbox systems and familiarize with the new technology upfront before they enter into customer projects from Dec. 10.
"Should you have any further questions please contact your local SAP account executive"
Also Please have a look at:
https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000692229&
Target Release to customer: Q4, 2007
Target Completion date Ramp-Up: Q1, 2008
Re: What is MDM?
https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=3226958
Getting Started with SAP NetWeaver Master Data Management [original link is broken]
https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=1757063
https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3408029
https://forums.sdn.sap.com/click.jspa?searchID=4313192&messageID=2857409
https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3442957
https://forums.sdn.sap.com/click.jspa?searchID=4313133&messageID=3687977
Re: Is SRM 6.0 (SRM 2007) released for non-ramp up customers?
Config UI not change
Do let me know.
Regards
- Atul

MDM number generation with length limitation

Dear experts,
I'm currently working on an MDM project, and creating a repository that will auto-generate Project Master number.
The tricky part is that the project number is alphanumeric: it is a combination of AABBCCCC.
AA = Site code (like CZ, XJ, etc)
BB = year (like 14)
CCCC = 4 digits auto ID (0001, 0002, ...., 9999)
I'm thining of using calculated fields, but I'm not sure how I can control the length of auto-id.
Any suggestions?
Thank you!
Best regards,
AZ

Hi AZ,
You can't control the length of auto-d, because its automatic generated unique integer key repersenting the count of the record in the table. The autoid is non editable and once deleted you can not get the code back for other records.
Kindly note there is no limitation for Autoid, as much records get created in the MDM table where autoid field is called,that much Autoid will get generated.
the below calculation you can use to achive your result.
Note:In the calculation field Right (Autoid,4) is holds value 4 so the autocodes will only generated till autoid9999. If you want to increase you can increment the value to 5, by that you can get the autocode till 99999.....
As you know any modification to the calculation field you require to stop the repository, to avoid this you can achieve this by using Assignment.
the below thread will explain and give you some idea regarding calling the assignment in the workflow.
http://scn.sap.com/thread/3521976
Regards

Hyperion MDM OS support memory limitation

Hi ,
I want to know that is Hyperion MDM is contrained by Operating System to support no more than 2 GB of memory?
Does it true for DRM 9.3.2 and Version 11 also?
If yes...Can it still support more than 80,000 member data into a single verion of DRM hierarchies?
Please help me to get answers of this problems.
Thanks

There is a new 64 bit version of DRM coming mid year that should do away with many of the memory issues. You should contact your ORACLE rep for a proper roadmap.
Can you elaborate a bit on what you will be doing that you anticipate that volume. I have been involved in many implementations and I know that right now there are at least 3 Oracle customers that have over 1M and are running DRM successfully.

Limiting field values of a tuple of MDM

Hello Experts,
I have a tuple in which there are 4 fields i.e. coloumns. Now my requirement is to limit the values of one of the fields of the tuple based on some condition.Please suggest which java API will help me out.
Regards,
Rohit

I would suggest modeling your tuple using Object Orientation.
If you do that you can add constraints into your object in the constructor and and any modifier methods.
This is because Object Orientation lets you bind data and methods that act upon them into a single data type.
http://en.wikipedia.org/wiki/Object-oriented_programming

Retrieving lookup field values from a main table using MDM JAVA APIs

Hi all,
am trying to retrieve the main table data...., i could able to retrieve all the data except lookup field values..., iam facing some runtime exceptions and i dont know why exactly it is throwing this exception..., i pasted piece of code where exactly the error is and the exception also.
in the below sode i set some result set definitions and passing them to retrieveLimitedRecordsCommand. it is showing some exception at retrieveLimitedRecordsCommand.execute(); command.
//*** Code ***//
supportingMainResultDefinitions = new ResultDefinition[] { rdQual ,rdFlat, rdqFlat };
 retrieveLimitedRecordsCommand.setResultDefinition(rd);
 retrieveLimitedRecordsCommand.setSearch(new Search(tableId));
 retrieveLimitedRecordsCommand.setSession(sessionId);
 retrieveLimitedRecordsCommand.setSupportingResultDefinitions(supportingMainResultDefinitions);
 try {
 retrieveLimitedRecordsCommand.execute();
 PrintRecords.toConsole(retrieveLimitedRecordsCommand.getRecords());
 } catch (CommandException e) {
 e.printStackTrace();
//*** Below is the Exception raised ***//
java.lang.UnsupportedOperationException: Unexpected field type -1
 at com.sap.mdm.internal.schema.PropertiesHelper.createField(PropertiesHelper.java:274)
 at com.sap.mdm.internal.schema.PropertiesHelper.convertFrom(PropertiesHelper.java:281)
 at com.sap.mdm.internal.data.RecordMetadata.<init>(Unknown Source)
 at com.sap.mdm.internal.data.RecordsLoader.<init>(Unknown Source)
 at com.sap.mdm.internal.data.RecordsLoader.<init>(Unknown Source)
 at com.sap.mdm.internal.data.RecordResultSetHelper.convertFrom(Unknown Source)
 at com.sap.mdm.data.commands.RetrieveLimitedRecordsCommand.execute(Unknown Source)
 at com.sap.mdm.apitutorial.lesson2.RecordsDisplay.getDisplayRecords(RecordsDisplay.java:303)
 at org.apache.jsp.Sample_jsp._jspService(Sample_jsp.java:190)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:362)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Thread.java:534)
If anyonw worked on this concept..., please provide me the solution
Regards
Praveen k

Which version are you using? Can you please try and narrow down to the offending field? You can do this by limiting the fields you provide to ResultDefinition.

How to map lookup main table field in another main table using MDM 7.1?

We created a new SAP MDM 7.1 repository with multiple main tables. The first main table is called ProductMaster table which contains Products information. The ProductCode is the primary key and the only display field for the table during data loading process. The second main table is ProductByRegion table which has a main table lookup field ProductCode and a RegionId field. These two fields (ProductCode and RegionId) combine as the PK for this main table. Both main tables have key mapping enabled.
I was able to load ProductMaster table using Import Manager. But Iu2019m having trouble to load data into ProductByRegion table using MDM Import Manager. Although I have met all the 5 requirements below (excerpted from MDM Import Manager Reference Guide P.222), the ProductCode wonu2019t show up on the destination value pane. If I mapped all productCode to NULL field, ProductCode wonu2019t load. If I u2018Addu2019 all ProductCode to Destination Value pane, the Import Manager added duplicated rows to Product Master table while only loading 1 record to ProductByRegion table. I canu2019t get ProductCode show up in Matching Destination Field list. When I checked ProductMaster records in MDM Data Manager, I right-clicked on one of records, chose Edit Key Mappings, it didnu2019t show anything. However, if I right-clicked on one of those duplicated rows, Edit Key Mapping shows remote system and key correctly.
Where did I do wrong? How can I fix the problem?
Thank you for help in advance.
From: SAP MDM Import Manager Reference Guide:
Mapping to Main Table Lookup Destination Fields
Import Manager handles main table lookup fields (Lookup [Main])
differently than other MDM lookup fields. Specifically, Import Manager
does not display the complete set of display field values of the records
of the underlying lookup table. Instead, the values it displays for a main
table lookup field are limited by both the key mappings for the lookup
table and the values in the source file.
Also, Import Manager does not automatically display the values of a
Lookup [Main] destination field in the Destination Values grid when you
select the field in the Destination Fields grid. Instead, for a main table
lookup field value to appear in the Destination Values grid, all of the
following conditions must be met:
u2022 The lookup table must have key mapping enabled
u2022 The lookup field must be mapped to a source field
u2022 The source field must contain key values for the lookup table
u2022 The destination value must have a key on the current remote system
u2022 The destination valueu2019s key must match a source field value
NOTE ►► The current remote system is the remote system that was
selected in Import Manageru2019s Connect to Source dialog (see
u201CConnecting to a Remote Systemu201D on page 416 for more information).
Vicky

Hi Michael,
Thank you very much for your response. I'm new to SAP MDM, I need some clarification and help regarding your solution.
I did use two maps to load ProductMaster and ProductByRegion separately. Here were my steps:
1. create main table ProductMaster with key mapping enabled at the table level and set ProductCode as unique and writable once (primary key).
2. create a map to load ProductMaster record from a staging table located an oracle database. But Key mapping didn't show anything when I looked at them using Data Manager.
3. create main table ProductByRegion with a lookup field looking at ProductMaster table. This field and RegionId combines as a unique field for ProductByRegion table.
4. create a map to load ProductByRegion table. But ProductCode records only shows on the source pane not destination pane and can't be mapped properly.
My questions:
1. How can I "Ensure that you add key mapping info for all ProductMaster records" besides enabling Key Mapping on the table level?
2. How can I define a concatenation of ProductCode and RegionId as a REMOTE KEY"?
Thanks a lot for your help!
Vicky

Assign records to different remote systems in MDM

Hello Experts,
I am using qualified range to generate internal number range for vendor. The remote key & remote system details for the records are generated during syndication. My scenario is that I have couple of records in MDM for different remote systems. I want to syndicate it to the respective systems. Is there a way to identify the respective records per system with out inserting the details in "edit key mapping".
If we try specifying Remote system details in edit key mappings with a blank or specific Key value , then the qulaified number generated for vendors is overwritten with this key value mentioned in key mapping.
I need to retain both the qualified range functionality as well as tag the records to different remote systems.
Kindly advice.
Thanks and Regards,
Elizabeth.

Hi Shiv
So, i am not sure, but this all makes me feel that syndication tasks can not be executed parallel.
Your understanding here is correct since we are using here the same table for syndication process so it will be executed in steps. I mean syndication 2 has to wait until the syndication 1 ends. But the thing is that even after syndication 1 completes syndication 2 is not going to place that's the issue here.
Please find solution which tells same thing in MDM import manager context.
Can I run two Import Managers at the same time?
Yes, several instances of the Import Manager can be open concurrently. The only existing limitation though is when actual importing process starts the tables involved in the importing process are locked for write access. So if two instances of the Import Manager import to different tables then no synchronization issue occurs. If they use the same table, then the instance getting access second has to wait until the first ends.
For more details, Please refer this below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7dc6ba86-0501-0010-0b82-849437929f0d?quicklink=index&overridelayout=true
@ Elizabeth: After Syndication 1, Have you checked after sometime whether syndication2 & so-on takes place or not. I feel that Syndication for syndication 2 , syndication 3 & syndication 4 should also occur after some time as they executed one by one not parallel so will take some time. Just check and revert with result whether your workflow gets completed after some time or not.
Note: Make sure that for all these Syndications outbound ports Processing Type = Manual in Console else syndication will not occur.
Regards,
Mandeep Saini

Error While Activating BI Web service data source based on MDM XI.

Dear experts,
Need help with an error that i am getting for a BI data source based on XI MDM. An extra field was added in the data source as part of business requirement and it works fine in dev environment but when we transported the changes to Q environment it is always giving following error.
The web-service based communication structure in the data source in QA is not getting updated with the new field in the target system.
Any inputs or pointers would be appreciated.
Thanks,
Abhishek

Many thanks for your help. This solved the issue for our .NET code, however the leak is still present in the report designer. I was also wondering if you could help further: because of the limits on the java memory process is there a way to ensure that a separate java process is started for each report that is loaded in my report viewers collection? Essentially the desktop application that i have created uses a tab control to display each type report, so each tab goes through the following code when displaying a report and closing a tab:
Is there a way to ensure that a different Java process is kicked off each time that I display a different report? My current code in c# always uses the same Java process so the memory ramps up. The code to load the report and then dispose of the report through closing the tab (and now the Java process) looks like this:
    private void LoadCrystalReport(string FullReportName)
      ReportDocument reportDoc = new ReportDocument();
      reportDoc.Load(FullReportName, OpenReportMethod.OpenReportByTempCopy);
      this.crystalReportViewer1.ReportSource = reportDoc;
    private void DisposeCrystalReportObject()
      if (crystalReportViewer1.ReportSource != null)
        ReportDocument report = (ReportDocument)crystalReportViewer1.ReportSource;
        foreach (Table table in report.Database.Tables)
          table.Dispose();
        report.Database.Dispose();
        report.Close();
        report.Dispose();
        GC.Collect();
Thanks

SRM-MDM Catalogue Search UI - Qualified table search

Hi,
We are having the following situation:
- We have a catalogue of articles
- We have to tie an article to a location, in addition to a location-specific parameter.
- Exampe:
Article A is tied to location A, parameter A
Article B is tied to location B, parameter B
Article C is tied to location A, parameter B
- The way to solve this in MDM is to use the qualified table. I have created one where:
Location = non-qualifier
parameter = qualifier
I want to make this searchable in the SRM-MDM search UI.
The user should be able to choose one Location, and then one parameter tied to that Location, to view relevant articles.
This is no problem using SAP Portal with MDM. But how can we realise this using SRM-MDM search UI?
I have tried, but can only get a drop down or text search on the non-qualifier field.
Can anyone please help? Is this even possible?
KR;
Thomas

Hi Thomas,
Is there any possibilities to configure/add code to the search UI, or is this completely locked for customization/altering through code? Unfortunately, I feel it is standard and we can not customize it.
There is no issue in your design but if your location as well as parameter has certain(limited) number of values only. You can create location field in MDM Main table which is lookup to Locations Flat table and similarly for Parameter field lookup to Parameters table rather than using Qualified table. As you can set lookup/Text field search only, so you can set these two fields in your search criteria. where first you search for Location say US it will search records with US location and when you further give search according to parameter it will further filter(navigate) records based on both Location and parameter, just a thought came which i feel to share with you, try it if it helps you.
Regards,
Mandeep Saini

Problems with posting iDocs from MDM in SAP R3

Hi,
I am an MDM consultant, with limited knowledge about SAP R3.
We send material master data from MDM, via PI to R3 using iDocs.
We are having problems with posting MATMAS, and it seems the problems are with updating already existing materials.
In BD87 we get the following warnings:
The field MARA-ERVOE is not ready for input and was therefore not initialized
The field MARA-ERVOL is not ready for input and was therefore not initialized
The field MARA-FERTH is not ready for input and was therefore not initialized
The field MARA-KZGVH is not ready for input and was therefore not initialized
The field MARA-XCHPF is not ready for input and was therefore not initialized
With the last message being:
No changes made
I have checked the MDM syndicator, and none of these idoc-fields are linked to the MDM repository.
So they are syndicated blank.
If we try to resend the material, it is again stopped and in BD87 I see the same messages.
Please help me understanding how to solve these issues.
Thanks,
Thomas

Hi,
Please refer the below threads which talks about the similar problem
http://scn.sap.com/thread/3180116
http://scn.sap.com/thread/1374222
Generally the basic view of the material to be created first. Then the sales, purchasing and other views to be created.
There are few fields in the other views which gets values from the basic data view.
Regards,
Antony

Error while using Import Manager in MDM 7.1 SP7

Hi,
We are using MDM 7.1 SP7. I am trying to import a Tab delimited flat file through import manager. When I try to connect the source file, I get the following error * Logon Error: Found non-complaint CSV format in input stream [Encoding:UTF16].96*
If I try to import through an excel there is not problem. Can someone help to solve this error while importing in Tab delimited flat file through import manager.
Best Regards
Manoj

Hello Mandip,
I had tried doing it before posting my question. I saved it in UTF8 and then tried importing. Saving in UTF8 format made the import manager accept characters like Ä and the original error was solved, but when then a new error came which called for UTF16 format. When I digged into it I found that it is due to the double quotes(" ") in the flat file. When I removed the quote import manager accepted it.
So the conclusion is there should be a way to save the flat file in UTF16 format or the workaround is importing it in excel but again excel has limitation of importing 100000 records in one file.
Can you suggest how to save the flat file in UTF16.
Best Regards
Manoj

More than 2 dropdown boxes in the UI Configuration/SRM-MDM Catalogue Search

Hi! We know that there is a limit to the number of drop-down boxes we can define in SRM-MDM UI configuration. However, we really have a need for that as there is no variant configuration in SRM-MDM. In this case, we want to allow user to select the colour (dropdown box) followed by size (dropdown box) in order to get the right items (e.g. shirt) to appear. Because we also need to have another field to be drop-down, we cannot do so due to the limitation.
Has anyone found a solution around this?
Cheers!
SF

No response on this.

MDM limitations?

Similar Messages

Maybe you are looking for