Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

    Add support for placeholders for stored procedures, to ODBC/JDBC drivers

    The existing [as of 7.0.5.00.01] drivers for TDV do not support SQL placeholders (bind parameters), when used with stored procedures. Using PERL or Python, the following kind of code fails: PERL: ---- use DBI; use DBD::ODBC; my $dsnName = 'DSN_N...
    over 8 years ago in Spotfire Data Virtualization / JDBC / ODBC / ADO 0 Future Consideration

    Ability to share library folder for import export in clustered environment

    Right now if we have clustered environment for spotfire and if you click on import/export option in library admin active servers folder is visible. If we are not using a shared folder or drive we cannot see folder of other servers. It should be po...
    over 8 years ago in Spotfire / Library 5 Will not implement

    Distribution Fitting- Poisson: Plot the first value of the Poisson fit over the entire area for X = 0 (i.e. from -0.5 to +0.5, not only from 0.0 to 0.5.

    Please see the attached file of a typical output, which shows that the expected value is only plotted over one half of the interval centered at zero.
    almost 9 years ago in Spotfire Statistica 3 Future Consideration

    Ability to call utilize the tables/graphs/etc generated from one workspace in another workspace

    Hi, I would like the ability to run a workspace (via a node or another means) within another workspace. The idea is that I can use the workspaces in the vein of object oriented programming, by having a "base class" workspace that could do somethin...
    almost 9 years ago in Spotfire Statistica 6 Already exists

    Use sigma from input data to calculate runs rules in QC analysis module

    At present, the sigma used for evaluating the runs rules violations is always calculated using the input measurement data. It is possible for the user to define the sigma to use for all other calculations (ie. http://documentation.statsoft.com/STA...
    almost 9 years ago in Spotfire Statistica 1 Future Consideration

    Allow for folder wide control over access to Business Author

    I understand that we can disable use of Business Author on a specific analysis file, but would like to be able to control at the folder level in much the same way as accessing analyses is controlled, perhaps by adding 'edit' or some other option a...
    about 9 years ago in Spotfire / Library 0 Future Consideration

    Enhancement request for option to keep old lmgrd records or not overwriting the old records when server is restarted

    Concurrent license manager generates lmgrd.log. We have built our own "license monirtor" which use lmgrd.log. But When the server restarts , lmgrd.log will be truncated. So we want lmgrd.log not to be truncated. Related Case 01527347 How to monito...
    about 9 years ago in Spotfire Statistica 0 Future Consideration

    Use LS means in the post hoc calculations of GLM.

    Currently observed means are used, and especially for ANCOVA designs one would prefer that the LS means which are corrected for the covariate(s) be used. See my case nr 01525480 for more details and examples. SAS, SPSS and R provide post hoc tests...
    about 9 years ago in Spotfire Statistica 0 Future Consideration

    New library method that returns all library items recursively

    This targets a current performance issue in our solution. The getChildItems() method only returns the library items inside a given folder. If we need to look into all folders inside the given folder, we need to make another call to getChildItems. ...
    over 9 years ago in Spotfire / Library 3 Future Consideration

    template in-memory compression

    hello folks,it's my understanding that QlikView, Tableau and other tools, do a very good job of in-memory compression of data.Currently, we have some very large templates with embedded data, that on disk are approx 1-2gb, however, in RAM (webplaye...
    about 10 years ago in Spotfire / Library 0 Future Consideration
    The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group LLC. All rights reserved. This page and your use is governed by these Terms of Use.