Skip to Main Content
Spotfire Ideas Portal
ADD A NEW IDEA

Ideas

Showing 729 of 4820

Web Data Entry: Seperate rights to create Data Entry Setup and entering/approving data

At the moment, a Data Entry Admin (EDE Permission) is able to enter, delete data and edit already approved data (HEDIT). Customers want to be able to separate these two areas. Therefore, it would be needed to remove the hidden rights (DE, HEDIT) f...
about 4 years ago in Spotfire Statistica 2 Already exists

Web Data Entry: Allow entering revisions based on role and not for a specific user

At the moment, if an entered sample needs revision and is set to status "Requires Revision" by an Approver/Admin, only the initial data enterer is able to enter the change. This person might not be available in a reasonable time frame, leaving the...
about 4 years ago in Spotfire Statistica 1 Needs Info

Support JSON data

Allow opening of data in JSON format
over 8 years ago in Spotfire / Data Access 3 Future Consideration

Allow saving data source credentials with cloud only solution

When trying to develop visualization to share with clients, I have to physically upload and embed the data every day, which is very inefficient. The data from Azure SQL is not sensitive, so I should be able to make the risk decision as the adminis...
over 6 years ago in Spotfire / Data Access 2 Future Consideration

Run the same workspace as task in a taskset with different parameter settings

Each AC can only be contained once as a task in a MAS taskset. The option to run workspaces with parameters is described in the Statistica help topic "Overview: Batch Processing Using Workflows and Statistica Enterprise Server". The idea is to run...
about 4 years ago in Spotfire Statistica 1 Future Consideration

Option to use label lists as input for acknowledge MAS alarm comments

When users acknowlege MAS alarms, they can enter a free text comment for each alarm. When customers want to analyze these alarms later, they have to do text mining. If only certain values from a list of label values are (optionally) allowed as a c...
about 4 years ago in Spotfire Statistica 0 Future Consideration

Improve support of datetime precision beyond milliseconds

Spotfire is struggling with anything below milliseconds for various reasons Especially in the light of a streaming extension it seems a bit outdated to only support milliseconds. But even in a more classical set-up when using timestamps to identif...
almost 4 years ago in Spotfire / Data Access 0 Future Consideration

Support for timestamp with timezone data type

Datasets from sources that use a timestamp with timezone field are read incorrectly in Spotfire. See: https://support.tibco.com/s/article/Values-in-a-column-of-type-Timestamp-with-timezone-are-different-from-original-values-when-imported-through-I...
about 2 years ago in Spotfire / Data Access 1 Future Consideration

Parameterize column selection of information link to reduce DB load and RAM usage

Hello everyone, to provide standardized information links to Spotfire users it would be very useful to have a option to parameterize the column selection of a information link. Goal is to keep database load and RAM usage under control by loading o...
over 1 year ago in Spotfire / Data Access 2 Future Consideration

Spotfire should support INOUT Parameters for RedShift Stored Procedure

Engineering team has determined this as an enhancement (which is kind of what we expected) as this is a relatively new feature in Redshift. There is an internal enhancement created for this to determine what it takes to support Redshift procedures...
almost 5 years ago in Spotfire / Data Access 1 Future Consideration