Issue with filter groups when inserting new record

Marco284
Member Posts: 1
Dear Community,
If certain filters are applied (e.g. by a view or a link) and the user creates a new record, then the fields affected by the filter are filled automatically. So far so good.
More specifically, the following case is at issue:
The user creates an extended text for an existing item. He opens the extended texts through the item card.
Because of the RunPageLink property the following filters apply:
In addition to that, a security filter is applied through the permission sets for that user:
That means in total the following filters apply:

Although the filters for the field No. do not contradict each other, they are also not identical, which causes that when a new extended text is created, the field No. in the record is no longer filled and the extended text is therefore not assigned to the item (in this case NL1000005).
This problem has nothing specifically to do with the item or extended text table or security filter, but can always be reproduced when two different filter groups work.
Does anyone have an idea how to work around this, so that in this case the field No. is filled and the table relation works?
Thanks!
Best regards,
Marco
If certain filters are applied (e.g. by a view or a link) and the user creates a new record, then the fields affected by the filter are filled automatically. So far so good.
More specifically, the following case is at issue:
The user creates an extended text for an existing item. He opens the extended texts through the item card.
Because of the RunPageLink property the following filters apply:
Table Name=CONST(Item), No.=FIELD(No.)If the user would create a new extended text now, the fields Table Name and No. would be prefilled.
In addition to that, a security filter is applied through the permission sets for that user:
Extended Text Header: Table Name=Item,No.=NL*
That means in total the following filters apply:

Although the filters for the field No. do not contradict each other, they are also not identical, which causes that when a new extended text is created, the field No. in the record is no longer filled and the extended text is therefore not assigned to the item (in this case NL1000005).
This problem has nothing specifically to do with the item or extended text table or security filter, but can always be reproduced when two different filter groups work.
Does anyone have an idea how to work around this, so that in this case the field No. is filled and the table relation works?
Thanks!
Best regards,
Marco
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 320 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