Home
Login
Sign Up
Infor - IBM i-series Community
Profile Options
Tools
Edit Profile
Manage all aspects of your profile here including demographics, emails, notification settings, etc...
Change Password
Begin the password change process
Email Subscriptions
Manage your opt-in/opt-out email subscriptions
View Profile
View your profile - what other's see
Sign-out
Sign out of this community
1-800-819-1190
Contact support line
Smart Connect
Connect with others and manage various member options
View QR Code
View your profile QR Code - Connect and or share your contact information
Tour Page
Take an interactive tour of this page
Knowledge Base
Visit the knowledge base for more info
Insights
Member reporting and analysis
Terms of Use
Cookies
Privacy Policy
Contact Us
Notifications
Notifications
Help
 
 

Site Menu

Message
Nick Olson Infor LX User Group
BC:
Build Strong Object Relationships đź”—
Establishing proper object relationships in IDF ensures seamless navigation and accurate data retrieval. Here are key relationship types:

📌 1-to-Many (Parent-Child) – Example: A Customer can have multiple Orders.
📌 Many-to-One (Lookup) – Example: An Order Line is linked to an Item Master.
📌 Code File Relationships – Ensure dropdown lists work properly.

A well-structured relationship model allows: Read more...
✅ Faster Data Access – Reduce queries and errors.
✅ Better UI Navigation – Quickly jump between related records.
✅ More Accurate Reports – Prevent missing or duplicated data.

If your relationships are messy, your system suffers! Need help setting them up? Let’s discuss in the comments! 👇 #InforIDF #DataModeling #ERPDevelopment Show less...
Delivered Read
Uncategorized
2
1
Latest msg: Another key consideration when defining relationships is the 'Bidirectional' option. Nick provided the example of a 1 to Many relationship from a Cus... from David Rapacz, on 03/27/2025

Comments (1) (Descending Chronological Order)
There are no comments at this time, be the first to comment

David Rapacz
BC:
Another key consideration when defining relationships is the 'Bidirectional' option. Nick provided the example of a 1 to Many relationship from a Customer object to an Order object. In this case, I would also suggest making this a bidirectional relationship which then also creates a Many to 1 relationship from Order to Customer. This then allows you to view all Customer attributes in an Order view when the Customer attributes are not part of the Order object itself, (ie Customer Name, CSR,  Read more...etc).  Show less...
2

Online