Problem setting up Client Data Source Substitution in v7.3+
Defect Fixed
I have YF configuredto have a primary organization and two client organizations. I am attempting tosetup client data source substitutions for each of the clients.
I have followed theinstructions outlined in:
http://wiki.yellowfin.com.au/display/USER73/Content+Management
As well as:
I am having a problemspecifically with the step outlined in bold (i.e. I do not see a place in thedata source builder that allows me to associate a data source with a specificclient.)
· create a data sourceand view at the default organisation
· create the globalreport against this data source
· create theclient-specific data source connection, and set it up to besubstituted for the default data source for a particular client
Hi Durwin,
Do you have a few minutes to screen-share this afternoon? If so please let me know what time works best for you. I am on US Mountain Time,
Regards,
Nathan
Hi Durwin,
Do you have a few minutes to screen-share this afternoon? If so please let me know what time works best for you. I am on US Mountain Time,
Regards,
Nathan
Hi Durwin,
Unfortunately it appears that this is a bug in the 7.3+ release. As this is core functionality, I have raised a defect with very high priority and informed some of our lead developers. Since this appears to be a purely visual problem, I am hopeful that we will have a fix for this within the next week.
In my tests this is specific to 7.3+ so if you are interested in seeing how this works in the mean-time, I would recommend installing a fresh copy of 7.3
Sorry for the bad news here and I will keep you up to date on the status of this.
Regards,
Nathan
Hi Durwin,
Unfortunately it appears that this is a bug in the 7.3+ release. As this is core functionality, I have raised a defect with very high priority and informed some of our lead developers. Since this appears to be a purely visual problem, I am hopeful that we will have a fix for this within the next week.
In my tests this is specific to 7.3+ so if you are interested in seeing how this works in the mean-time, I would recommend installing a fresh copy of 7.3
Sorry for the bad news here and I will keep you up to date on the status of this.
Regards,
Nathan
Hi Nathan,
we just installed the most recent version "Yellowfin BI 7.3 Plus - build 20170630" and this issue has not been resolved. Do you have any update as to a resolution time?
Thanks,
Durwin
Hi Nathan,
we just installed the most recent version "Yellowfin BI 7.3 Plus - build 20170630" and this issue has not been resolved. Do you have any update as to a resolution time?
Thanks,
Durwin
Hi Durwin,
My apologies, it appears that this fix was pushed back a month and is marked to be included in the end of July release.
There may be something we can do to get this to you sooner. I will look into this and stay in touch.
Sorry for the inconvenience.
Regards,
Nathan.
Hi Durwin,
My apologies, it appears that this fix was pushed back a month and is marked to be included in the end of July release.
There may be something we can do to get this to you sooner. I will look into this and stay in touch.
Sorry for the inconvenience.
Regards,
Nathan.
Hi Nathan,
In have fresh installed "Yellowfin 7.3 - build 20170606" but seems have similar this bug. The client views use the default data source not its one.
In default data source Usage Parameters, the client data source list is empty although exists 1.
Please feedback whether this bug exists on this build or not. Will use newer version will fix it?
Best regards,
Kevin
Hi Nathan,
In have fresh installed "Yellowfin 7.3 - build 20170606" but seems have similar this bug. The client views use the default data source not its one.
In default data source Usage Parameters, the client data source list is empty although exists 1.
Please feedback whether this bug exists on this build or not. Will use newer version will fix it?
Best regards,
Kevin
Hi Kevin,
Yes this issue has been fixed in the most recent builds:
Nathan
Hi Kevin,
Yes this issue has been fixed in the most recent builds:
Nathan
Hi Nathan,
Thanks. Confirm that I upgraded to 7.3 latest build and the issue was fixed.
Kevin
Hi Nathan,
Thanks. Confirm that I upgraded to 7.3 latest build and the issue was fixed.
Kevin
Glad to hear it.
Glad to hear it.
Replies have been locked on this page!