Skip to main content

Hi,

I got a "MODAL" which is a separate DSP from the "MAIN" page. Before the "MODAL" is closed an operation of "MAIN" is called to pass new information on a new occurrence of an entity, the problem comes that after this all the other entities are emptied of their data.

My guess is that it has something to do with the pre and postactivate triggers or maybe I'm missing something else.

Regards.

Hi,

I got a "MODAL" which is a separate DSP from the "MAIN" page. Before the "MODAL" is closed an operation of "MAIN" is called to pass new information on a new occurrence of an entity, the problem comes that after this all the other entities are emptied of their data.

My guess is that it has something to do with the pre and postactivate triggers or maybe I'm missing something else.

Regards.

Hi Alejandro,

I suppose a quick debug session can help you to focus your guessed doubts or to let them vanish totally... 🙂

Regards,
Gianni


Hi,

I got a "MODAL" which is a separate DSP from the "MAIN" page. Before the "MODAL" is closed an operation of "MAIN" is called to pass new information on a new occurrence of an entity, the problem comes that after this all the other entities are emptied of their data.

My guess is that it has something to do with the pre and postactivate triggers or maybe I'm missing something else.

Regards.

Hi Alejandro,

It sounds like your scope is the issue. 

I am going to take a guess at your trigger flow being the trigger/operation in MODAL and MAIN are both server-side. 

;trigger in MODAL
trigger detail
public web ; trigger is callable directly from the browser
scope
	input
	output
	operation MAIN.myOperation ; include data defined by the scope block in MAIN
endscope
	activate "MAIN".myOperation()
end
; operation in MAIN
operation myOperation
partner web ; Can contain a scope but can't be called directly from the browser
scope
	input ; Send data to the server
	output ; Data will be return - block the DSP to prevent race conditions
endscope
	webmessage "In Main"
end 

Kind regards,

Mike


Hi Alejandro,

It sounds like your scope is the issue. 

I am going to take a guess at your trigger flow being the trigger/operation in MODAL and MAIN are both server-side. 

;trigger in MODAL
trigger detail
public web ; trigger is callable directly from the browser
scope
	input
	output
	operation MAIN.myOperation ; include data defined by the scope block in MAIN
endscope
	activate "MAIN".myOperation()
end
; operation in MAIN
operation myOperation
partner web ; Can contain a scope but can't be called directly from the browser
scope
	input ; Send data to the server
	output ; Data will be return - block the DSP to prevent race conditions
endscope
	webmessage "In Main"
end 

Kind regards,

Mike

Hi Mike, thanks for the reply.

I did some testing with the scopes but it didn't worked so I solved it with JS and a hidden field.