Disable DME object from being Actionable?

Does something happen when users click into the 2nd DME? This type of control is usually a JavaScript script.

Yes, it tries to pass values to a 3rd DME query. The issue we have is that the 3rd DME is mapped to the first DME query similar to the 2nd DME; since what we are trying to show is the AR applications that exists against AR invoices. The problem is Lawson has 2 types of applications, invoice applications and credit appllications but both are stored in the same file..ARAPPLIED. Depending on the first DME query (which is against the AROITEMS file) row click either the 2nd DME or the 3rd DME query will render results. It's ok to render both DME queries, even though only one will be populated; we just don't want the user to be able to click on either the 2nd or 3rd DME query results.

Okay, these types of changes/updates either occur because you've scripted them to or because you've done some data mapping. To disable you will need to update your Portal Page design. I can't tell you how to disable since I don't know what you've done to enable. Do you have a Design Studio expert on hand or did someone design these for you?

We enabled the DMEs using the standard index Trigger Refresh in DS (no JAVASCRIPTING). I believe the problem is that since both the 2nd and 3rd DMEs are mapped to the 1st, it's causing the issue. We designed them ourselves using the standard DS toolset since we do not have a JAVASCRIPT expert on site.

Here is a little javascript code that might help you get started. I do believe you'll need javascript though.

[code] var dmeData1 = page.objects["am002_data1"] var dmeData2 = page.objects["am002_data2"] dmeData1.autoHide = true dmeData1.hide = false dmeData1.forceRefresh = true; dmeData1.refresh(); dmeData2.autoHide = true dmeData2.hide = true dmeData2.forceRefresh = true; dmeData2.refresh(); [/code]

Thanks Terry for the javascript; however, we do not want to hide the DME we only want to keep the user from clicking on a row in the DME. Any suggestion on how to do this?

So you want this to be like a header/detail?, where clicking on a different record on DME1 (header) changes display in DME2 (details)?=