DMP Posted November 27 Posted November 27 Hello, I have 3 reports in a Development environment where multiple document properties are automated by data functions (no iron python). Some are very easy expressions such as First() of a specific column and some are more complex but they work perfectly. In the Development environment, the data is connected to a sandbox (not live data) of a program management software. In Development environment, I can edit and make changes to the reports. After, these 3 reports get put into Production environment (connected to live data and updated 4 times a day), some document properties, don't work and some do. They appear blank even for some simple data function formulas like First(). I verified that the data in the column of the expression First() is there and it should work. Sometimes if I simply toggle between some filters of data (on and off and on again) it activates the document properties and the correct value appears. The filter is usually not even related to the document property or any expression in the whole report. How can I get all of the document properties to work all at once like they do in Development?
David Boot-Olazabal Posted November 27 Posted November 27 Hi DMP, Since you move your files from Development to Production, may we assume that the underlying data sources are also 'different' (dev vs prod)? And if so, are the data source connections updated in the analysis files you move to Production? To rule any possibility of name changes/typos in the Production environment, are you able to check the failing document properties and the data function scripts that are used to populate them? I mean, can you check and fix the issues in Production to see what has gone wrong? Also, can you tell us what Spotfire version you are working with? Kind regards, David 1
David Boot-Olazabal Posted November 27 Posted November 27 Hi DMP, Just to add to the above. As your request involves troubleshooting, it's a bit in a grey area between what we do in the Community and involving our Support team. I certainly would advise you to file a support case via http://spotfi.re/support. Especially if there is an urgency to get this solved quickly. Kind regards, David 1
barchiel33 Posted Wednesday at 12:50 PM Posted Wednesday at 12:50 PM Would any of your data sources happen to have caching enabled? I'm wondering if the report is loading with it's data loaded and the data function only triggers when something changes.
DMP Posted Wednesday at 10:59 PM Author Posted Wednesday at 10:59 PM @David Boot-Olazabal The data sources are different. Development is working from Program Management Software Sandbox (not live data). Production is working from Program Management Software (live data). Yes, the data source connections are updated in the analysis files when moved to Production. The data is verified and confirmed showing and updating correctly in the data tables. Even some of the document properties show correct values so it works in some cases. and some only appear when turning on off fields in the filter panel. In the two screen shots shown above, the document property is using a simple First() expression for the column that only have F082024MEC as the only possible value in that column of the Data Table. The issue is that I can't check the failing document properties, and the data function scripts in Production. Can only view the Dashboard. Spotfire Version is 14.0.3. @barchiel33 I don't have the ability to check in production but in development I have attached screenshot. Not sure if this is what you are asking.
David Boot-Olazabal Posted Thursday at 07:47 AM Posted Thursday at 07:47 AM Hi, When the deployment to Production is done, I would suggest that the same persons (administrators?) who do that, not only change the data source connection, but also check the way this analysis file works. In particular the data functions that trigger the document properties. As you are unable to do that yourself, the only way to find out, is that someone does this exercise and see what and where it goes wrong. It may be that the data function parameters needs to 'reconfirmed' to make them stick (since there has been a data source change). But we can only find out if this is done by someone. Once we know what happens, we can tell whether this is normal behavior (or not) and what to do (or who to involve) to solve it. Kind regards, David
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now