Passing data between modules not working properly
Application Type
Reactive
Service Studio Version
11.14.8 (Build 58515)

It's about an exercise of Boot Camp Training. An application with two modules: principal and “core”.


At “core” there is a “Server Action” which triggers an SQL:



Till here, everything is ok. The expected structure comes with all the values:



In the main module, there's a call to the above mentioned Server Action:


The returned content is:


Just two values are returned.

Both strucutures are identical.

Any idea about what may be wrong?

Thanks in advance.

Bookings_Assayag.oap

Hi @RAFAEL ASSAYAG ,
Good Day !

just now I gone through your OAP file, You have doe a fantastic job.

Here below are some changes I'm sharing

1) Use Data action for SQL so that Check-In date ad Check-out date you can pass it from main module other than using core module which you had created GetAvailableRoom server action passing input parameters.


2) By just using refreshing Data action you can achieve your Requirement.


Please check the attached OML.
Please check the below link.

Link : DMEO Link

I hope this helps ad you will get a proper solution.

- Palle Vijay Bhaskar Reddy

DataAction Use OML.oml

Thanks Vijay,

While I waited for your help, I observed a very strange behavior in the process. I found out that the two attributes exposed on the sreen, after the fetch, where returned. So I simply exposed the attribute I needed and it has worked!

I will however, adopt your approach.

Thanks once more!

Hi Rafael,

No problem was found in the shared module. I think you will publish the modules and refresh the used modules.

Then it will be work.

Regards,

Shahaji




Hi @RAFAEL ASSAYAG ,
Good Day !

just now I gone through your OAP file, You have doe a fantastic job.

Here below are some changes I'm sharing

1) Use Data action for SQL so that Check-In date ad Check-out date you can pass it from main module other than using core module which you had created GetAvailableRoom server action passing input parameters.


2) By just using refreshing Data action you can achieve your Requirement.


Please check the attached OML.
Please check the below link.

Link : DMEO Link

I hope this helps ad you will get a proper solution.

- Palle Vijay Bhaskar Reddy

DataAction Use OML.oml

Thanks Vijay,

While I waited for your help, I observed a very strange behavior in the process. I found out that the two attributes exposed on the sreen, after the fetch, where returned. So I simply exposed the attribute I needed and it has worked!

I will however, adopt your approach.

Thanks once more!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.