+3I have created a dataset from data designer with it to be permanent and update daily. I want to add to a dashboard and have a global filter applied from the Company object since the other reports on the dashboard pull from that object.
Is this possible?
Best answer by rakesh
This is released and is in production.
Whenever you bring in a field such as User Name, also bring User Id till the last dataset. We understand that you want mapping (our mechanism to identify special fields) and will treat that user name field as a special user field that can be used in global filter and report filters.
+1Hi
It should already be possible to add a dataspace based report to Global Filter for most fields in dataspace. However, we do not automatically understand mappings information yet (=> This is a work in progress item) and hence there should be a challenge adding Company Name, User Name, Account Name fields to the global filter. Without propagating this mapping information, a special field such as Company Name becomes a text. We are working on it internally and expect to ship this relatively soon.
+1Hi
+1This is released and is in production.
Whenever you bring in a field such as User Name, also bring User Id till the last dataset. We understand that you want mapping (our mechanism to identify special fields) and will treat that user name field as a special user field that can be used in global filter and report filters.
+3I believe some of this is solved but is it still not possible to create a lookup from the Company Object to a Data Designer Dataspace? This would be immensely useful and solve a lot of issues we have, especially with the primary use-case here.
Please advise or link to any documentation on this update so I can re-review :)
+1+3When merging in DD, from the company object I included the CaseSafeID, GSID, Account Name, CSM GSID, CSM SFDC ID and was able to associate them with global filters, although it was only with reports based on that object, the “Account Name” field was a link to the C360 so I presume it will also work when using these reports embedded in a C360 section as well.
tl:dr
+3
Create a custom object and then have a rule upsert to the custom object. You can add a lookup on the custom object fields and then report from there.
It would be a much better experience however to add a lookup directly in a dataset like you are able to in a custom object
+10What might I be doing wrong?
+4
Hi ,
This should work as expected if users select CSM GSID from nested fields section instead directly selecting from the CSM look up. This has been the behaviour from the start and changing this now will have backward compatibility.
Scenario 1 (CSM ID will be a text field in Reports)
Scenario 2 -( CSM ID will be an ID field)
As you see below, when CSM GSIS was selected from the nested fields section it appeared as a ID in reports but when it was selected directly from the CSM look up, it appeared as a text field
Do let us know if you still have some concern(s)
+2This is sort of solved but it would still be RAD if the MDA objects created by Data Designers allowed lookups to be created, so that you could use lookups when reporting on those objects. Even when you look at them in Data Management, they have the column for lookup (which you can’t edit) staring tantalizingly at you like a forbidden data fruit.
Appreciate the potential workarounds but +1 for a cleaner solution!
+1+1, data designer objects would greatly benefit from lookups
+1 as well, painful loss of functionality requiring inefficient workarounds
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
