Hello Rod,

After doing some testing, I think the problem is the url property is caching.  If you have multiple Event modules with corresponding Event Detail modules configured properly to operate from different pages,  the url property for the "Back" button redirects to the first Event Module that was viewed....

For example, let's say I have two Event Modules (A & B) setup on different pages, and Event Detail (C & D) modules setup on different pages.  If I view Event Module A, select to view a new event, it will direct me to the correct Event Detail module.  When I hit the Back button, it returns me to Event Module A.  Now, if I go to the other page containing Event Module B, select to view an event from Module B, it directs me to the correct Event Details module for Event Module B.  The problem is when  I hit the Back button, it will redirect me to Event Module A.

This seems pretty consist.  I think the easiest solution would be to hardcode the return tab value for the Back button url.  This would allow the control of the url to the appropriate tab value.  This is an easy value to retrieve, and is the way I hardcode values for navigation in other modules.

I need to resolve this fairly quickly, as it will delay my deployment of the module into production.

Any thoughts or ideas?

Thanks again,

JD