Visokio website     Downloads     Video tutorials     KnowledgeBase  
Insert column and data on table view and prevent that column from loads - Visokio Forums
Insert column and data on table view and prevent that column from loads
  • Focus_Media Focus_Media April 19, 2011 2:18PM
    Hi, working on the table view we need to insert some data on a new column created for those.

    The question is if there is any way to fix that data in a way that when we update the data manager we don`t lost the data included by the user.

    I explain what is happening. We need to point some of the data using users criteria, for instance valorate the urgency of an actions that must been taken in a scale of 1 to 3. We create a new column in a way user can insert its valoration (we are going to use this valoration to work in another iok file). We fill the new column and save, the problem came when we update the data from the sources because the columns created by users lost the data.

    There is any tip or way to block the columnt and don't allow it to be updated.

    Thank You
  • 2 Comments
  •     steve April 19, 2011 4:02PM
    Let's say your data has a unique ID field "ID" and the user is entering data in the new field "Valoration".

    Add a File Output block, and choose to save to a file adjacent to your other files, such as "User changes.iok".
    After the user has made changes, they should click "Publish" in this block.

    Now add the "User changes.iok" block as a File source block.
    Insert a Join/Merge operation immediately upstream of the Omniscope block. Connect the "User changes.iok" to the 2nd input of Join/Merge.
    Configure Join/Merge to match by the "ID" field and to only import "Valoration" values, overwriting existing fields.
    When you refresh, you should find the user's changes are being merged back in.

    You can repeat this process:
    - user makes edits to "Valoration" field
    - user clicks Publish
    - user refreshes from source (Ctrl+F5)
    - (new data + user changes are automatically merged).

    You can choose more complex operations and merges if necessary to support more complex data models but the principle is the same: the user's changes are saved to a separate file, which is then merged in using an ID field.
  • Focus_Media Focus_Media October 6, 2011 5:46AM
    Works fine, thanks a lot, sorry for the delay :-)
Add a Comment

Welcome!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

Tagged