Intelliwarp with multiple entities

On our radar
The ability to drag Excel spreadsheets and create tables with data in Intelliwarp is fantastic for creating quick screens around a single entity type. And it makes for an amazing demo capability. But the ability to do the same for multiple related entities would make it much more powerful, in particular for prototyping.

Currently if you have data on 2 sheets the wizard creates Entity1 from Sheet1 and Entity2 from Sheet2, but these entities are not linked. After Service Studio has created them and the data has been bootstrapped it's difficult to associate them correctly within the tool and get the Foreign Key data right. I would like to be able to put the parent data on Sheet1 and the child data on Sheet2 with FK values and load it correctly, creating the relationship during the process. The Intelliwarp wizard could ask the user at loading time how/if they wished to relate FK columns.

I actually did manage to do this with three hierarchically related entities in three different sheets and a small amount of data by guessing that the Ids that would be allocated would be sequential, loading the data, and then redefining the FK columns, but it was not simple.

This feature has great potential for quick starting projects and increasing productivity if you make it a bit more sophisticated.
Created on 16 Jul 2010
Comments (2)

I'd like to enhance this request in that if you pick an entity from a list you have built and that it has foreign keys to other entities that intelliwarp gives you the option of building not only single screens for table selected and its related table but also multiple 1:M screens based on the FK attributes of the entities.

These can be easily removed if not required and would speed up the process quickly.

By default I would like to see 4 screens created for any single entity.

Create, Read, Update and Delete and a similar strategy for all linked tables.

Changing the Intelliwarp usage into a simple step-by-step wizard should provide the flexibility to do all the above requests as well as the scalability to add new features later on. 

Whilst the current process is a major breakthrough from 4.2, the fact remains that the drag-n-drop approach without further user interaction or ability for customization might become an impediment later on.