Has anyone come across this issue that some events are not triggered but some are?

As of CacheAttached in graph extension, it should not be executed. CacheAttached is purposed for replacing/extending attributes of DAC. I would be surprised, if CacheAttached would be executed. Outside graphExtension and Graphs, yeah, may be cases when CacheAttached will be executed. As of RowUpdated, RowUpdating not being executed, I seen cases when usage of three input parameters ( cache c, rowupdatedEventArgs e, RowUpdated baseDelegatePointer)prevented execution of some events. That happened, when baseDelegateEventPointer was never executed. Another case I seen, when AddHandler/RemoveHandler was executed. Below goes a link for samples of AddHandler: http://blog.zaletskyy.com/post/2023/06/15/how-to-add-handler-to-graph-dynamically

@darylbowman correct. CacheAttached works for attributes, and not for execution of the body. It’s Aspect Oriented Programming feature of C# ( AOP ).

If you want to target CacheAttached, you may need to look into attributes, and 

PXEventSubscriberAttribute class.

Below goes code sample of how actual implementation for CacheAttached, which will be triggered by debugger:

public class BCCustomNumberingAttribute : PXEventSubscriberAttribute
	{
		protected String Dimension;
		protected Type Mask;
		protected Type Numbering;
		protected Type NumberingSelect;

		public BCCustomNumberingAttribute(String dimension, Type mask, Type numbering, Type select)
		{
			Dimension = dimension ?? throw new ArgumentException("dimension");
			Mask = mask ?? throw new ArgumentException("mask");
			Numbering = numbering ?? throw new ArgumentException("numbering");
			NumberingSelect = select ?? throw new ArgumentException("select");
		}

		public override void CacheAttached(PXCache sender)
		{
			base.CacheAttached(sender);

			PXCache bindingCache = sender.Graph.Caches[BqlCommand.GetItemType(Mask)]; // Initialize cache in advance to allow DimensionSelector from GuesCustomer fire events on persisting
			sender.Graph.RowPersisting.AddHandler(_BqlTable, PrioritizedRowPersisting);
		}

That is sample from Acumatica source code itself. 

But if you’ll apply that in graph, or graph extension, it will not be executed.

As far as I know, PXRestrictor will be applied without execution of CacheAttached method. Acumatica uses CacheAttached only for reading of the attributes, not for execution of the body of CacheAttached itself.

Which screen you try to customize? Which Acumatica version you use?

@Yuriy Zaletskyy Thanks for looking further into this odd thing.

• I am testing on 22.212.0046.
• The graph you are extending is the Expense Receipt graph. It works fine in the extension as you pointed out.
• The Screen I try to customize is Daily Field Report (PJ304000)
• The Primary Graph is DailyFieldReportEntry
• The Primary DAC is DailyFieldReport
• The tab I have this problem with is “Labor Time and Activities”
• Its DAC is EPActivityApprove which lives in “PX.Objects.EP.EmployeeActivitiesApprove” and is a projection DAC from PMTimeActivty
• Its Associated View in the graph context is EmployeeActivities that lives in DailyFieldReportEntryEmployeeActivityExtension Extension
• The field its CachAttached is not triggered is LabourItemID

Below is the exact code I am trying to make it work but cannot.

namespace Test
{
    public class TestExt : PXGraphExtension<DailyFieldReportEntryEmployeeActivityExtension, DailyFieldReportEntry>
    {
        public static bool IsActive() => true;

        #region EPActivityApprove CacheAttached LabourItemID
        [PXMergeAttributes(Method = MergeMethod.Merge)]
        [PXRestrictor(
            typeof(Where<InventoryItem.itemStatus.IsNotIn<InventoryItemStatus.unknown, InventoryItemStatus.inactive, InventoryItemStatus.markedForDeletion>
                    .And<InventoryItem.itemType.IsEqual<INItemTypes.laborItem>>
                    .And<InventoryItem.inventoryCD.IsNotLike<HCLINInventoryCategory.inventoryCategoryPRIM>>>),
            "Invaid Inventory Item")]
        protected void _(Events.CacheAttached<EPActivityApprove.labourItemID> e) { }
        #endregion
    }
}

Hi @aaghaei, I was able to reproduce the problem locally, but was overly busy for virtual dev con. Will try to find solution during tomorrow or Saturday.

You by all means welcome. I also lost couple of hours on that issue in the past as well. I’m going to record a YouTube video, which will explain it in more details, and will ask you to like it and share on your social media. 

@aaghaei tag Acumatica employees for suchlike requests. I will report on this one, but if for whatever reason I will skip, just tag potentially Chris Hacket or other people.

@sangland Thank you for chiming in. I am both an admin and an employee. If I am not an employee I won’t be able to even open the screen.