1 of 1 people found this helpful
We have datasources that are common to multiple workbooks. Where workbook-1 needs these-three calcs, and workbook-2 needs those-10 calcs, we make the calcs within the respective workbooks.
Thanks for the response Joe.
So this may come off as naive, but in regards to the calculated fields, are you saying that calculated fields can be part of the published workbook structure rather than the published data source structure?
Holy cow! I can't believe I didn't realize this or even try that. This works perfectly.
With this in mind my strategy could be as follows:
- Publish standardized Dept X data source
- Create one off calculations within workbooks themselves
- If a calculated field becomes common enough that it should be part of the standardized set, download a local copy, add field, re-publish
One follow up:
If I hide unused fields prior to publishing the workbook, will that improve performance or would that only be effective if the published data source had hidden unused fields?
Hiding unused fields doesn't improve performance in any way I know.