Acoustic Campaign Ideas

The Acoustic Ideas portal has moved! Please sign up for our new Ideas portal and submit your suggestions at

Relational Table Interface Revamp

I think everyone who uses relational tables know what I'm talking about when I say that we need a revamp to allow more functionality via the UI.  Here are some of the updates I'd love to see that will make this relational tables easier to use:

  • Add additional fields via the UI without having to do a new data import
  • Rename fields
  • Delete fields (if unused)
  • Easier export of relational table data (without using the API)
  • Value reports for relational table fields
  • Manually add contacts to the relational table
  • Auto-incrementing unique identifiers
  • Folders to organize relational table queries.

Would love to hear additional commentary from users about other features that could be added to relational tables to improve their usage.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 24 2018
  • Under Consideration
How will this idea be used?

Anyone who works with relational tables on a routine basis will find these improvements helpful.  I understand that working with relational tables and their maintenance is not a part of every user's regular work flow - but this is something that has been needed since pre-IBM days.

What is your industry? Non-Industry Specific
What is the idea priority? Low
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 11:14

    Hi There, We are currently about to go the relational table route and i just wanted to clarify your one point above. Are you saying that IBM WCA does not currently support the functionality to manually upload contacts or data into a relational table? 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 12:49

    Yes, I add one: functionality like update profile into RT. I mean establish values from a program.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 16:05

    Hi @Bianca,  it does - but you cannot manually add records one at a time like you can a standard database.  You can still do a standard data import.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 18:11

    I like most of the recommendations for RTs, but I caution on the renaming table fields or deleting them, especially if you have 3rd party integrations like SCRIBE. Changing the table field name or deleting fields is changing the mapping on those integrations and will most likely fail if not updated correctly. Other than that, I do like the other recommendations.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 18:40

    I will second on all of the above plus ability to update values from the program, especially if it will allow to update a specific record in RT when there is one:many relationship to main database

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 25, 2018 23:07

    Ideally it would be great to add default values to RT fields as is achieved with the masterdatabase.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 02, 2018 09:15

    All of the above and a few more:

    • Add to the above the ability to link to the same table in different ways for different use cases rather than having to duplicate the table. 
    • Make the RT content editor a WYSIWYG editor like the main editor and dynamic content has already.
    • Support tracked links for relational table content without having to build Dynamic Link Leader Links (DLL).
    • Allow querying of date time (timestamp) fields so that records with values between a particular date and time can be queried.
    • Support the use of child relational tables for Mobile Push and SMS Query
    • Support child relational tables for program entry queries and program flow
    • Support the use of relational table criteria in dynamic content


  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    July 14, 2018 09:03

    I would also add:

    #1. the ability to manually dis-associate relational tables from a database without using the API. So that they are easy to delete.

    #2. Automatic deletion of relational tables not used after a certain amount of time (450 days?).