joinCDT

RE: joinCDT

mayureshs — Mon, 28 Nov 2016 09:08:22 GMT

@Sally thanks for your suggestion,but the requirement to perform a join at interface level not at DB level, as it increases burden on Database.

RE: joinCDT

Sally Mason — Mon, 28 Nov 2016 09:01:52 GMT

Maybe there is another way to approach this issue? If an employee has many skills, you could make a view at the database level to retrieve and display all the skills and perform the join at that level and create a CDT to display the results?

RE: joinCDT

mayureshs — Mon, 28 Nov 2016 08:39:05 GMT

@Sally I have already tested "rule!MS_IAL_GetAllEmployeeDetails()", "MS_IAL_GetAllEmployeesSkills_CDTManipulation()" rules independently and it is returning expected data. actually these are query rules, i also tried with the query entity which is returning datasubset, but i don't think so this is valid solution, is it?

RE: joinCDT

Sally Mason — Mon, 28 Nov 2016 01:50:17 GMT

Appears to be that there is missing data causing the interface to fail..

Can you test "rule!MS_IAL_GetAllEmployeeDetails()" and "MS_IAL_GetAllEmployeesSkills_CDTManipulation()" independently and confirm that these two rules are returning the expected data and if no skills are returned, the null is handled?

RE: joinCDT

mayureshs — Fri, 25 Nov 2016 19:06:47 GMT

Hi tom PFA for complete application server log.

application-server.log

RE: joinCDT

Tom Ryan — Tue, 22 Nov 2016 11:01:15 GMT

Can you attach the complete application server log from when you reproduced the error.