There are at least three areas that I can currently create a calculated value.
However, if I want to have a Document Property to contain a calculated value, I can't do it without running some R code.
I would like to see an ability to create a property based on a calculated value.
You should be able to do this same types of things like "Limit By Marking" that you can in the other places you have a calculated value.
Be able to store a "calculated value" into a document property is key to pass results based on filtering and/or marking from 1 data set to another not related data set. This should be available without using R nor Python script, where on Python you can have calculated value (custom expression) as a parameter and the script only push the calculated value to the document property (Document.Properties["myproperty"]=calculatedValueParemeter). By avoiding this mandatory script to pass the result over the application, you'll reduce by far the risks (admin rights) and maintenance costs.
If we managed to do this, we would also be able to:
- send the results of calculations in our automation services emails, effectively enabling alerting
- be able to have the result of Spotfire calculations feed into TERR data functions, thus allowing calculations to happen where they are more efficient.
https://community.tibco.com/questions/there-way-update-document-property-when-filtered-data-changes-without-using-action-control
https://community.tibco.com/questions/do-you-know-if-it-possible-set-value-doument-property-based-other-document-properties
https://community.tibco.com/questions/i-written-r-script-get-filtered-data-document-property-i-getting-error
https://community.tibco.com/questions/can-i-set-document-property-marking-spotfire-v6
https://community.tibco.com/questions/set-document-property-using-script-marking
https://community.tibco.com/questions/passing-multiple-calculated-values-document-property
https://community.tibco.com/questions/changing-document-property-value-when-filter-applied
https://community.tibco.com/questions/passing-values-between-data-tables-calculating-values-document-properties#node-651001
To give details on use cases:
If I have an avg latitude and longitude from one table that I want to calculate the Great Circle Distance to for all the coordinates in another table, can't because there's no way to get at that calculated value without using R to pass them into the Properties. Oddly enough, the more complicated calulation (Great Circle Distance) is simply built in.
If there's a particular statisic (like an average line) that I want to use across multiple tables, I can't just have a globally calculated value without using R.
This would make the effort taken in this video no longer necessary.
https://www.youtube.com/watch?v=81vXShmDyOM
And this one would be much easier.
https://www.youtube.com/watch?v=qZA31cs-dEM