Filter function with a criteria
Dear Experts, I have a data like below( in columns A/B/C) , and needed the result in column (I/J/K), but I could achieve only like in Column (E/F/G) For example for the rnti = 19453, the corr0 , at time -> 06:34:32.171912 is not there so at Row-3, the entry should be empty Attached is the worksheet, Br, Anupam
Overlap bar chart help
Newbie here & very green :) I'm creating a bar chart with 2 sets of data: start date & end date. See pix. I created the bar chart, all the bar starts out on the same date!. I need help here. I need a single bar with start-end dates. A step-by-step lesson would be appreciated very much. Please help. Thanks!
Data in area chart not matching the source
Looking to see if anyone has any answers for my issue below. I am trying to track manpower for group A and B. In my table below, Group A is showing that their work will be completed in June. Group B is showing that their work will be starting in July. In my bar chart below, I am using it to visualize the data in the table above. The data shows that both groups are starting and completing in the correct months based off the data. In my area chart below, using the same data, I am using an area chart (which is preferred) to visualize this information. But the graph shows Group A completing in July and Group B staring in June. It shows that the work will be overlapping, which is not true. I am hoping that someone is able to help me figure out how to make the area chart correctly show the information from the table above instead of showing the workload overlapping.BUG REPORT: Microsoft Excel Table Versioning Incompatibility Breaks Macro Logic
Excel tables now silently behave differently based on internal "versioning" (version 1 vs version 2), which is undocumented, invisible to the user, and directly breaks macros that previously worked across all sheets. There is no native method to identify which version a table is using, and users receive zero warnings when behavioral changes cause critical automation failures. Impact: .ListRows.Count and .ListRows(lastRow).Range.Delete fail inconsistently depending on the hidden version type Developers are forced to rewrite macros—not for logic reasons, but to compensate for Excel silently violating expected object behavior No version flag exposed in the UI, VBA, Power Query, or formula metadata Breaks trusted workflows for trainers, dashboard builders, and automation developers—especially during live sessions or instructional demos Forces users into non-consensual, destructive workarounds like converting the table to a range and rebuilding it from scratch. This should never be necessary. A user should not have to destroy a structured object to restore its usability. Repro Steps: Create a table via "Insert > Table" (defaults to version 2 silently) Copy data from older workbook sheets (some revert to version 1) Run macro using .ListRows(lastRow).Range.Delete Logic fails, errors, or behaves inconsistently Only workaround: convert table to range and rebuild—which is professionally unacceptable Temporary Workaround: On Error Resume Next With ActiveSheet.ListObjects(1) Dim lastRow As Range Set lastRow = .ListRows(.ListRows.Count).Range If Trim(lastRow.Cells(1, 1).Text) = "" Then lastRow.Delete End With On Error GoTo 0 Call to Action: Microsoft must publicly acknowledge the undocumented and silent divergence in structured table behavior between internal “version 1” and “version 2” implementations. This regression has: Broken established VBA logic Caused hours of untraceable macro failures Forced users into destructive workarounds Undermined trust during live instruction, client deliverables, and advanced workflow design Provided no way for users to identify table version—this is unacceptable We demand: Full disclosure of structured table version differences—what changed, why, and when Visible version metadata in Excel’s UI, VBA object model, and Power Query Behavioral standardization across workbook sources and creation methods Permanent removal of forced workarounds like converting tables to ranges just to restore row deletion logic Public bug tracking, resolution timeline, and community updates If Microsoft cannot provide these answers, then Excel structured tables must be considered unstable containers for automation. Developers and trainers cannot build trusted systems on invisible rules and undocumented regressions.
