Perhaps this basic bit of functionality has been revealed and I just cant find the post yet. If so please do forward me in the right direction and forgive my humble inquiry, but I have hit the documentation and the forum search before asking ....

I have finally come upon a need to allow users ( specific security role ) to edit the content in a detail module of products in an e-commerce like application.   I need to identify the Key field they have selected to get to this "Item Detail" module, as they are now about to select the edit feature and change the product description.  I have recently mastered the Settings module as it does its TabModuleSettings saves. I am now in need of identifying the selected Item that brought the user to this item details page and make it available to the edit module such that I can now return the appropriate fields for their manipulation. I'll just run a query to return the editable fields based on this ItemId.  But I am not sure how to attack the problem of OBTAINING (Passing) [perhaps correctly storing and retrieving] the itemId from the View module to the Edit module. 

We know hoe the Settings module saves your settings and te view module reads them in from session,  so will that work fom View to edit module ??

Will I have the settings value available in the Edit module if I save it in the view module ... Yes I'm trying it now but perhaps theres a standard I can reference that I haven't seen yet.

Any assistance is greatly appreciated.

Respectfully,

With God's Will,

 C. Taylor Milwaukee

Thanks We can consider this closed.

As I mentioned !!!   I was basing my theory on my use of the Settings module.

I have developed a working solution based upon ASP.NET session varaibles.

My Search led me to some posts that suggested personalization.  Alas my initial thoughts were confirmed. Even for a multi user situation the Session variable works fine.  Your info on passing stuff in the querystring is interesting and I will try it some time but I inherently dont like it.  Your referring to DNN's ItemId and we bypass the default DNN dataaccess stuff.  My ItemId is a real ID from an item in one of our many customers databases per the "item" the user selected.      Thanks again I'll need to peek at this when I want to anvigate to pages in the future based upon Page name not the tabId....