Discussion posts and replies are publicly visible
You need to set a solid data structure first before building the grid and all! Build reference tables first with the static data your app needs. Like services should have a reference/ look up table having unique service id and services.
then plan table should have plan related details.
The main table , scenario, should have scenario details.
Another table should be there which stores scenario id, plan ids and services ids using foreign key references as they relate. If you use records then consider setting relationships.
Taking this general idea build your Interface. For a scenario get the plans and for plans get the services. It might seem pretty complex but using variables and process models you can pass data between interfaces (tasks). So start with tables then start designing your interface. Given my limited understanding of your use case you might need to tweak the data structure so adjust as needed and come back if you face challenges.
We have these tables already for scenario, plan, services and for one particular services I need to save the fee details i have created a table for that as well with service table id as foreign key. I am trying to create the fee details inside the grid where services details are populated and save that to table. But I'm not sure how to do it.
Use an editable grid showing services and fee details joined by service Id. Bind data to a local variable. On save, use a!writeRecords() to insert/update fee details in the fee table keyed by service Id. Reload data to sync after saving.