I'm looking at an example on page 546 of the VB version of the Business Objects book. So far I've objects being added to my collection and those objects show up in the gridview very nicely. I can cancel, add new and so on with no problems.
The multiview shows the grid with the current child objects and it also shows a view for the insert functionality. If the object is invalid on the insert screen it will still insert it into the collection (but not save it to the database) so that I've an invalid object in the collection.
That means I've the error message (or broken rules) showing up on the grid view screen when I'd rather have it show up on the insert screen - and prevent the insertion until the object is valid. I could create the object behind the DataSource.InsertObject event and not add it to the collection if it is invalid, I suppose - I dunno - I'd like to get some input on how others handle the creation of objects on the web and how broken rules are communicated to the end user.
Thoughts?
Copyright (c) Marimer LLC