Notifications

112 views

Description

Created a m2m table for 2 custom tables, configured the m2m table as a related list and created a list control for the related list to apply default filter.
In some case, on the first load, the filter will not be loaded correctly, as a result, some unwanted records are pulled in the slush bucket

Steps to Reproduce

1. Go to a Madrid demo instane
2. Create 2 custom table extending from task, Table one & Table two
3. Go to tab.list and create new
4. Set From table: Table One, To table: Table Two and Many to Many table: u_m2m_table_two_one
5. Create 2 new records on Table one, set one's active to false
6. Create a new record on Table two
7. Right click on the new table two record > Configure > related list
8. Add Table One related list to the layout
9. Right click on the Table one related list > Configure > List control
10. Add "Edit default filter" as Active is true > Save
11. Click on the "Edit..." button on the table one related list
Expected behavior: only one record should show
Actual behavior: 2 records shows on the left slushbucket
NOTE: If this is not happening, please try to repeat step 11 a few times or hop to another node

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available..


Related Problem: PRB1371416

Seen In

Madrid Patch 4
SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - Discovery and Service Mapping - 201908
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Quebec

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-08-13 22:56:52
Published:2020-07-08