Prev
Next
Forums Lawson Design Studio

Disable DME object from being Actionable?

Sort:
You are not authorized to post a reply.
Author
Messages
Eddie Smith
Advanced Member
Posts: 39
Advanced Member
9/27/2010 10:53 AM
    Is there anyway to disable a DME query result from being "actionable"? In other words,when a user clicks on a row in the first DME object, a second DME object is rendered; however, we would like for the second DME object to be static (i.e. non-clickable).
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    9/27/2010 11:44 AM
      Does something happen when users click into the 2nd DME? This type of control is usually a JavaScript script.
      David Williams
      Eddie Smith
      Advanced Member
      Posts: 39
      Advanced Member
      9/27/2010 12:01 PM
        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.
        David Williams
        Veteran Member
        Posts: 1127
        Veteran Member
        9/27/2010 12:10 PM
          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?
          David Williams
          Eddie Smith
          Advanced Member
          Posts: 39
          Advanced Member
          9/27/2010 1:07 PM
            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.
            Terry P
            Veteran Member
            Posts: 234
            Veteran Member
            9/27/2010 1:56 PM
              Here is a little javascript code that might help you get started. I do believe you'll need javascript though. 

              
		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();
              Eddie Smith
              Advanced Member
              Posts: 39
              Advanced Member
              9/27/2010 3:30 PM
                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?
                John Henley
                Senior Member
                Posts: 3348
                Senior Member
                10/21/2010 8:41 PM
                  So you want this to be like a header/detail?, where clicking on a different record on DME1 (header) changes display in DME2 (details)?=
                  Thanks for using the LawsonGuru.com forums!
                  John
                  You are not authorized to post a reply.