AugForums.com

An Acumatica User Group

  • Free
    • Start Here
    • In-Person Gatherings
    • Power BI Workshop
    • Podcast
    • Rolodex
    • Blog
    • Forums
  • Paid
    • AugSQL
    • GI Course
    • GI Library
    • Consulting
  • Register
Acumatica Forums

By using this website, you agree to our Terms of Use (click here)

Forums
AUG Forums
Acumatica Report De...
Error SO Report
 
Notifications
Clear all

Questions Error SO Report

 
Acumatica Report Designer
Last Post by Tim Rodman 6 years ago
6 Posts
2 Users
0 Reactions
2,303 Views
RSS
Posts: 3
 Berry Wijaya
Topic starter
January 27, 2020 11:08 pm
(@berry-wijaya)
Member
Joined: 6 years ago

hai everyone, i had an error issue report SO with the error code like this : 'Error #366: The report does not contain parameters: SOOrder.OrderType0, SOOrder.OrderNbr0.'

 

anyone can help me

sorry for my bad english


5 Replies
Tim Rodman
Posts: 3204
 Tim Rodman
Admin
February 9, 2020 8:08 pm
(@timrodman)
Famed Member
Joined: 11 years ago

Can you attach the .rpx file? Also, are you trying to run the report from a screen or independently from the Acumatica menu?


Reply
 Berry Wijaya
(@berry-wijaya)
Joined: 6 years ago

Member
Posts: 3
February 11, 2020 11:02 pm
Reply toTim RodmanTim Rodman

file attached, i try to run the report from the SO screen

 

so641010.rpx


Reply
Tim Rodman
Posts: 3204
 Tim Rodman
Admin
March 4, 2020 11:57 pm
(@timrodman)
Famed Member
Joined: 11 years ago

When a report is launched from a screen, the screen passes parameters to the report. The report has to have appropriately named parameters to receive what the screen passes to it.

The Sales Orders (SO301000) screen passes the following parameters:
OrderType
OrderNbr

So, your report has to have those two parameters or you'll get the error message that you're seeing.

Your report has these two parameters:
OrderType
RefNbr

Take a look at this standard Sales Order (SO641010) report to see the appropriate parameters setup and how they are used in the report:

SO641010.rpx

Also, note that you can change what parameters get passed to a report using some low code / no code techniques in a Customization Project. But simply changing the report parameters to match what the screen is already passing would be simpler in your case.


Reply
Posts: 3
 Berry Wijaya
Topic starter
March 9, 2020 9:59 pm
(@berry-wijaya)
Member
Joined: 6 years ago

Still same error when the report call from the Sales Order Screen->action-Print, but when call from the report menu no error

so641010.rpx


Reply
Tim Rodman
Posts: 3204
 Tim Rodman
Admin
March 24, 2020 7:52 pm
(@timrodman)
Famed Member
Joined: 11 years ago

I'm getting the same error message in my environment, but the error message doesn't make any sense to me.

One thing I did notice is that your report doesn't have any fields in the Groups:

Compare that to the standard report which does have field in the Groups:


Reply
Forum Jump:
  Previous Topic
Next Topic  
Forum Information
Recent Posts
Unread Posts
Tags
  • 12 Forums
  • 2,532 Topics
  • 11 K Posts
  • 20 Online
  • 2,418 Members
Our newest member: Chad Treadwell
Latest Post: Limited or no support from Acumatica?
Forum Icons: Forum contains no unread posts Forum contains unread posts
Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Online Members

  • Dianne A
Acumatica Forums

Terms of Use & Disclaimers :: Privacy Policy

Copyright © 2026 · AUG Forums, LLC. All rights reserved. This website is not owned, affiliated with, or endorsed by Acumatica, Inc.

‹›×

    ‹›×