Flowfield calcformula based on date range
sneha
Member Posts: 191
Here is my scenario:
Table1 fields are: Item No. , location code, Rate Effective Date, Rate
Table2 fields are: Item No. , Location Code, Ship Date, Table1Rate. Table1Rate is a flowfield.
Table 1 data is:
Apple, US, 03/01/14,$5
Apple, US,03/15/14,$6
Table 2 data is:
a) Apple, US, 03/04/14,Table1Rate, I need to show it as $5.
b) Apple, US,03/15/14,Table1Rate, I need to show it as $6.
Condition to pull the Rate into Tabl1Rate flowfield is:
Table1.Item No.= Table2.Item No.,Table1.Location Code = Table2.Location Code,Table1.Rate Effective Date <=Table2.Ship Date.
How should I write a calcformula for the above condition?
Table1 fields are: Item No. , location code, Rate Effective Date, Rate
Table2 fields are: Item No. , Location Code, Ship Date, Table1Rate. Table1Rate is a flowfield.
Table 1 data is:
Apple, US, 03/01/14,$5
Apple, US,03/15/14,$6
Table 2 data is:
a) Apple, US, 03/04/14,Table1Rate, I need to show it as $5.
b) Apple, US,03/15/14,Table1Rate, I need to show it as $6.
Condition to pull the Rate into Tabl1Rate flowfield is:
Table1.Item No.= Table2.Item No.,Table1.Location Code = Table2.Location Code,Table1.Rate Effective Date <=Table2.Ship Date.
How should I write a calcformula for the above condition?
0
Comments
-
Hi as you probably noticed, NAV isn't happy to accept < symbol in the flowfield definition.
One thing you might try is to add a new field to the Table 2 called "Price Date Filter"
This will be a text field. OnValidate of the Date field, put in '..' + FORMAT(Date) as the value.
Then your Table 2 data looks like this:
Table 2 data is:
a) Apple, US, 03/04/14,..03/04/14,Table1Rate, I need to show it as $5.
b) Apple, US,03/15/14,..03/15/14,Table1Rate, I need to show it as $6.
and the flowfield definition looks like this:
Condition to pull the Rate into Tabl1Rate flowfield is:
Table1.Item No.= Table2.Item No.,Table1.Location Code = Table2.Location Code,Table1.Rate Effective Date =Table2.Ship Date.
Alternatively, make it a function instead of a flowfield.
This would work well, but it doesn't allow you to filter, but filtering on a flowfield is kind of bad anyways.
- Reinhard0 -
Thank You Reinhard!
A new function logic worked better than a flowfiled.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 327 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions