Langsung ke konten utama

FATAL EXCEPTION PERFORMING AXRDCE TRANSFORMATION STEP. THE REPORT CANNOT BE RENDERED. PLEASE CONTACT YOUR SYSTEM ADMINISTRATOR.

FATAL EXCEPTION PERFORMING AXRDCE TRANSFORMATION STEP. THE REPORT CANNOT BE RENDERED. PLEASE CONTACT YOUR SYSTEM ADMINISTRATOR.


Today I came with new issue in AX Report.
Few days back my report was working fine.
But today it showed me something weird information while opening the report.
Fatal exception performing AXRDCE transformation step. The report cannot be rendered. Please contact your system administrator.
I was just googled, there is no luck. Finally I figured out the issue.
First this SSRS report was developed with Query Dataset type.
Few days before I just deleted one field from my table. but I checked in (Visual Studio) SSRS–> MyReport –> dataset –>fields 
still my deleted field is exist in this report dataset.
This is the only reason i got this error.
I have tried to delete the unavailable field, but there is no option to delete the field from Report dataset.
Here is the solution if you have same scenario.
  1.  Export the Report from AOT ( backup ).
  2.  Edit the Report in Visual studio.
  3. Note down the Report Dataset name, Query Name and it’s selected field from the Query windows as images shows below. You have to reuse this same dataset name and fields in next steps.1st
  4. Now delete the report dataset which contains unavailable fields.2nd
  5. Create a new dataset then put the same name as you noted in previous step and select the same Query and select the previously noted fields.
    1. Note : If you gave wrong datasetname your report will show error. Make sure u have given correct dataset name which previously noted.
  6. Save the report and deploy it.
Finally it’s worked. 🙂

Komentar

Postingan populer dari blog ini

Use X++ wildcard (LIKE and NOT LIKE) in X++ select statement

For x++ select statements:  select firstOnly batchHistory      where batchHistory.Caption  LIKE  "*Test*"  For x++ queries:  queryBuildRange.value(*Test*); Note the LIKE instead of a '==' and the wildcards inside of the quotations. All other combinations of wildcard usage will work here. This is the same functionality as what the users would put in the grid filtering(eg. '*TEST*' in the caption field filter on the batch tasks form).  However, if you want to find all Captions that do not have the word Test in them (NOT LIKE, !LIKE), you will have to modify the above example slightly.  For x++ select statements:  select firstOnly batchHistory      where  !( batchHistory.Caption LIKE "*TEST*" ) ;  For x++ queries:  queryBuildRange.value(!*Test*);

Format Label Tom Jerry (MS Word)

Setelah beberapa lama aku tidak membuat label undangan, tiba-tiba kemarin aku diminta untuk membuat label undangan Wisuda dengan menggunakan label merek Tom & Jerry (TJ). Harusnya sih menjadi tugas sekretaris panitia tapi karena yang bersangkutan ada tugas di luar kantor maka aku yang membereskannya. Mula-mula aku membuat format labelnya dengan cara manual, tapi untung ada pak Mulyadi (staf tata usaha) yang menyarankan aku untuk mengunduh format label yang telah ada di Internet. Mulailah aku browsing di google dan menemukan format label berbagai ukuran dari website Tom & Jerry di alamat berikut  http://tjlabels.com/en/download.html  (yang link ini agak rempong krn pake masukin nomor captcha-captcha-an). Sedangkan kalau yang link ini langsung pilih file ga pake nomor captcha-captcha-an ( http://tjlabels.com/assets/download/ ). Ternyata juga ada banyak berbagai blog yang menyediakan  link download seperti ini, tapi aku mem- posting  artikel ini ...

Solved : Update on a valid time state table is not allowed without specifying a ValidTimeStateUpdateMode

How To Solve Error :  Cannot edit a record in Position hierarchies (xyz). Update on a valid time state table is not allowed without specifying a ValidTimeStateUpdateMode. select forUpdate * from xyz where xyz.recid== _RecId ; try { ttsBegin; _Value= “Abcd”; xyz.Name = _Value; xyz.validTimeStateUpdateMode(ValidTimeStateUpdate::Correction); xyz.ValidFrom =today(); xyz.ValidTo=dateMax(); xyz.update(); ttsCommit; } catch { ttsAbort; }