{"id":5634,"date":"2014-08-31T12:20:29","date_gmt":"2014-08-31T12:20:29","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=5634"},"modified":"2018-11-19T10:54:10","modified_gmt":"2018-11-19T10:54:10","slug":"how-to-pass-dynamic-data-in-crystal-reports-from-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2014\/08\/31\/how-to-pass-dynamic-data-in-crystal-reports-from-x3\/","title":{"rendered":"How to pass dynamic data in Crystal reports from Sage X3"},"content":{"rendered":"

While working on a crystal report we come across the situation where we want to process data from several tables before running the report.\u00a0 In this situation X3 provide specific coding feature where we can write code to pull data from several tables and screens and we can pass to Crystal report before running. We can also enforce business rules while processing these data sets.<\/p>\n

Using this feature, you free up lot of links that you had to use in Crystal report. This way, you are going to use more than one table to pull data, pass only final processed table to Crystal report which will reduce complexity and load on the Crystal report. In certain scenarios, this will also improve performance.<\/p>\n

New Stuff: <\/strong><\/em>How to execute export utility through code<\/a><\/p>\n

\"Dyn-1\"<\/a>Syntax : –<\/strong><\/p>\n

$ACTION
\nCase ACTION
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 When ‘EXEC’ : Gosub EXEC
\n<\/strong>\u00a0\u00a0\u00a0 Endcase
\nReturn<\/p>\n

$EXEC<\/p>\n

\/\/ Here we can write our complex code or call parameterized, non-parameterized function to pull data.<\/p>\n

Return<\/p>\n

While working with X3 you can avoid some limitation of Crystal report also.<\/p>\n

Like –<\/p>\n