AUGForums.com

An Acumatica User Group

  • Free
    • Start Here
    • Rolodex
    • Podcast
    • Blog
    • Forums
  • Course
  • Consulting
  • Login
  • Register
Acumatica Forums

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

  • Overview
  • Member List
  • All-Stars
  • Stats
  • Recent Posts
  • Help
Forums
AUG Forums
Acumatica Report De...
Add production orde...
 
Notifications
Clear all

In order to allow me to focus on Consulting (click here) and Courses (click here), I continue to review all posts here in the Forums, but, in general, I'm only personally responding to posts that I mark as #AcumaticaTnT (click here). For Questions (click here), others may respond, or you can post over at Community.Acumatica.com (click here).
Sincerely,
Tim Rodman

Questions Add production order attributes to production ticket report AM625000

Acumatica Report Designer
Last Post by LT8675309 8 months ago
3 Posts
2 Users
1 Likes
301 Views
RSS
LT8675309
Posts: 14
 LT8675309
Topic starter
June 11, 2022 2:29 pm
(@ltussing)
Member
Joined: 1 year ago

I have added 2 attributes to a production order.  I want to print these on the production order ticket report AM625000.

I added AMProdAttribute to the report with the following relationship.

 

I then added 2 new Text Boxes to the report with the following values:

=IIf( [AMProdAttribute.AttributeID]='STARTCASE', [AMProdAttribute.Value], '' )

 

the second box has this value

=IIf( [AMProdAttribute.AttributeID]='ENDCASE', [AMProdAttribute.Value], '' )

 

The first box prints as desired, but the second does not print anything.  

​​

Here are the only records in AMProdAttribute:

 

Any suggestions are greatly appreciated!!!!!

2 Replies
Royce Lithgo
Posts: 544
 Royce Lithgo
June 12, 2022 10:01 pm
(@roycelithgo)
Member
Joined: 3 years ago

STARTCASE and ENDCASE are from different records. At the point you are printing them on the report, both records can't be active at the same time. I think you need to save the data in variables and print the variables in the report.

Actually the better approach would be to join AMProdAttribute twice, one for each Attribute ID. In the join conditions, and the criteria for AttributeID value - then you will only have one record per Production Nbr. With your current approach you are duplicating data for Production Nbrs due to the multiple Attribute ID values - this just makes things difficult.

Reply
LT8675309
Posts: 14
 LT8675309
Topic starter
June 12, 2022 10:29 pm
(@ltussing)
Member
Joined: 1 year ago

Thanks for the reply Royce.

I got around this by making an attribute with a format of xxxx-xxxx.  The first 4 characters are the starting number and the second four numbers are the second number.

Sincerely, thank you for taking the time to respond and what you said makes sense.

Reply
Tim Rodman reacted
Forum Jump:
  Previous Topic
Next Topic  
Forum Information
Recent Posts
Unread Posts
Tags
  • 11 Forums
  • 2,239 Topics
  • 9,872 Posts
  • 7 Online
  • 1,813 Members
Our newest member: Marion Hooley
Latest Post: Export Scenario - Export same row twice (Conditionnal)
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

Acumatica Forums

Terms of Use & Disclaimers :: Privacy Policy

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

‹›×

    ‹›×