Data Designer - Limit of 50 Show Fields for the Merge

I agree that the 50-field limit feels restrictive, especially since we don’t allow dataspaces created via data design to lookup to other objects. Which means you need to include everything you might need in that data design. If you think about it, you usually have access to hundreds of different fields when sourcing from just about any standard or custom MDA object. 

Also, the UX is unfriendly when displaying the 50-field limit. It doesn’t say how far over that limit you are, so you just have to uncheck fields until the error message disappears.

Yes to everything @spencer_engel said! The 50 field limitation is going to be incredibly restrictive for us. Why would you limit my reporting capability? :( Please consider resolving in the very near term!

@elliot_hullverson FYI

Recently I faced the 50 fields limit issue with Data Designer. Any plans on increasing this limit.

I also would love this to be increased, especially for folks on the SFDC platform.  Im sure this is not really an issue for NXT, tee hee :)
A scenario we face is (unfortunately) some of our SDFC fields have been designed with incorrect field types, that don’t allow us to aggregate, as an example.  Our SFDC team in under-resourced, so to have them re-do the field to the proper type may take some time..

Instead of creating a data space for a specific solution, we would want to create a data space that can encompass multiple workflows.  

For example, let’s say that our case object has about 5 fields we cannot use for aggregation/charting, in addition, we also have to merge it with the account object so we can pull account attributes.  We would want to use data designer to create a ‘new’ case object that would pull as many as the case fields we would need for various reports down the road, not just the one report we want create right now.  

It makes it really messy if we constantly build data spaces for specific reporting solutions

Hi All,

It is possible to increase this limit. However, when we increased the limit from 50, we have observed that when there are a lot of fields (especially from inside lookups) and data sets, the UI isn't as responsive. Hence we did not increase the limit for everyone. 

Let me know here if you understand this tradeoff and would still like me to increase this limit and I can increase it only for your instance. 

@rakesh thank you for the heads up.  Personally, I would like to test this in a sandbox environment to see what the UI slowness looks/feels like to better determine the tradeoff.  I think 75-100 would be (for me) the perfect number of number of fields to have an output.  This will ensure that the MDAs we create are robust enough that they can be used for multiple work streams, making the overall tool more versatile and efficient (vs having to create a data designer for each work stream or report need)

Additionally, I would like to add an enhancement request to see if Gainsight can holistically look at the slowness and enhance the overall framework of data designer (if at all possible)

A possible but messy workaround is to do a data designer of a previous data designer and add to that.  From an administrator perspective, it can get a little messy and hard to manage.  

@rakesh  I’m running into this as well - it wouldn’t be a problem, though, if Data Designer was able to dynamically honor lookups between MDA tables.  Part of my issue is that I am having to manually pull in fields from Company → User lookup into this data set.  If I could just pull in the SFDC Account ID and have it auto-lookup to the Company → SFDC Account ID, I wouldn’t have to pull in more than 50 fields to the merge.

I have hit this limit also combining a complex request object in SFDC to the Call to action object. That combination can easily go over 50 for a comprehensive data space to cover all the options. Also, fully agree with @darkknight on  honoring lookups to save field bandwidth. We can do our own workarounds at that point. 

I see this post is tagged implemented. Is that a mistake or was this addressed recently?

Hi @alex_legay  
Its 50 by default for all customers. You can increase it by raising a support ticket. (Recommended to not go beyond 100)

Also, technically, we cannot have lookups when you use Data Designer. 

@rakesh can we also increase Show Me limit in Rules Engine? Running into this issue when trying to pull in files from S3.

Looks like the current limits is 100, but that is still insufficient.  Why is there a limit?  If there needs to be a limit, please stop making us replicate string fields and prevent us from using lookups outside Data Designer.