How does GLTran DAC manipulate the FinPeriodID

Hi ​@MatthewMyersDR,

Have you tried with using same declaration of FinPeriodID field of GLTran Dac in your custom DAC?

#region YourFinPeriodIDField
public abstract class yourPeriodIDField : PX.Data.BQL.BqlString.Field<yourPeriodIDField> { }
protected String _YourPeriodIDField;
[PXDefault]
[FinPeriodID(
    branchSourceType: typeof(GLTran.branchID), 
    masterFinPeriodIDType: typeof(GLTran.tranPeriodID),
    headerMasterFinPeriodIDType: typeof(Batch.tranPeriodID))]
[PXUIField(DisplayName = "Period ID", Enabled = false, Visible = false)]
public virtual String YourPeriodIDField
{
	get
	{
		return this._YourPeriodIDField;
	}
	set
	{
		this._YourPeriodIDField = value;
	}
}
#endregion

Please try to declare like this in your custom DAC for period ID.
Hope, it helps!

To display financial selector need to add UsrOrganizationID,UsrBranchID,UsrOrgBAccountID field with attribute then UsrCommissionPeriod​ defined it.

#region UsrCommissionPeriod​

[PXDefault()]​

[AnyPeriodFilterable(null, typeof(AccessInfo.businessDate),​

branchSourceType: typeof(usrbranchID),​

organizationSourceType: typeof(usrorganizationID),​

useMasterCalendarSourceType: typeof(AccountByPeriodFilter.useMasterCalendar),​

redefaultOrRevalidateOnOrganizationSourceUpdated: false)]​

[PXUIField(DisplayName = "Commission Period", Visibility = PXUIVisibility.Visible)]​

public virtual string TSCommissionPeriod { get; set; }​

public abstract class uSrCommissionPeriod : PX.Data.BQL.BqlString.Field<uSrCommissionPeriod> { }​

#endregion​

​

Added by moderator: This reply has been created with the help of AI

You need to work with a DB-calculated formula or a helper field in your custom DAC.

1. Understand the Stock Behavior

The stock GLTran DAC likely uses a display-only attribute or a calculated field to format YYYYMM into MM-YYYY for presentation. When used in a Generic Inquiry (GI), this transformation is handled seamlessly by the system.

2. Create a Display Field for FinPeriodID

You can create a calculated field in your DAC that manipulates the YYYYMM value into the desired MM-YYYY format.

Example Implementation:

#region FinPeriodIDFormatted [PXString(7, IsUnicode = true)] [PXUIField(DisplayName = "Fin. Period (Formatted)")] public virtual string FinPeriodIDFormatted { get { if (string.IsNullOrEmpty(this.FinPeriodID)) return null; // Swap YYYYMM to MM-YYYY return $"{this.FinPeriodID.Substring(4, 2)}-{this.FinPeriodID.Substring(0, 4)}"; } } public abstract class finPeriodIDFormatted : PX.Data.BQL.BqlString.Field<finPeriodIDFormatted> { } #endregion 

• The FinPeriodIDFormatted field is a calculated property that takes the stored FinPeriodID (in YYYYMM format) and reformats it to MM-YYYY.
• Use Substring to extract the last two digits (month) and the first four digits (year) from FinPeriodID.

3. Add to Generic Inquiry

In Generic Inquiries, include the FinPeriodIDFormatted field instead of the raw FinPeriodID. This field will display the MM-YYYY format for easy filtering and reporting.

4. If You Need a DB-Level Transformation

For database-level manipulation, you can use a SQL-calculated field by specifying the formula in your DAC using the PXDBCalced attribute.

Example with PXDBCalced:

#region FinPeriodIDFormatted [PXDBCalced(typeof(Substring<GLTran.finPeriodID, int4, int2> + "-" + Substring<GLTran.finPeriodID, int0, int4>), typeof(string))] [PXUIField(DisplayName = "Fin. Period (Formatted)")] public virtual string FinPeriodIDFormatted { get; set; } public abstract class finPeriodIDFormatted : PX.Data.BQL.BqlString.Field<finPeriodIDFormatted> { } #endregion 

• This SQL-calculated field will dynamically generate the MM-YYYY format for the FinPeriodID column at the database level.

5. Align with UI/Filtering Expectations

Ensure the field aligns with UI expectations:

• Add [PXUIField] to ensure the field appears correctly in forms and inquiries.
• Use the formatted field in reports, screens, and GIs where users need MM-YYYY.

Summary

• Use a helper property or DB-calculated field to format YYYYMM to MM-YYYY.
• The Substring method allows splitting and reordering of the string.
• Use the formatted field in UIs and GIs for consistent user interaction.

#region YourFinPeriodIDField
public abstract class yourPeriodIDField : PX.Data.BQL.BqlString.Field<yourPeriodIDField> { }
protected String _YourPeriodIDField;
[PXDefault]
[FinPeriodID(
    branchSourceType: typeof(GLTran.branchID), 
    masterFinPeriodIDType: typeof(GLTran.tranPeriodID),
    headerMasterFinPeriodIDType: typeof(Batch.tranPeriodID))]
[PXUIField(DisplayName = "Period ID", Enabled = false, Visible = false)]
public virtual String YourPeriodIDField
{
	get
	{
		return this._YourPeriodIDField;
	}
	set
	{
		this._YourPeriodIDField = value;
	}
}
#endregion

I tried implementing this code and the field results were blank.

Ok so I’ve made some progress, however I still have a problem.  When I use this field in my DAC and try to specify a condition on that field, it does not honor the conditions and returns all records.  Here is my field, what am I doing wrong?

[PXString(6, IsKey = false, IsUnicode = true, InputMask = "##-####")]
[PXDBCalced(typeof(Add<BQL.Substring<GLTran.finPeriodID, int5, int2>, BQL.Substring<GLTran.finPeriodID, int1, int4>>), typeof(String))]
[PXUIField(DisplayName = "Period ID")]
public virtual String FinPeriodID { get; set; }
public abstract class finPeriodID : BqlString.Field<finPeriodID> { }

Thank you for your assistance.

I think I have it working the way I need it to.  Here is my current solution.

 

#region FinPeriodID  
[PXString(6, IsKey = true, IsUnicode = true, InputMask = "##-####")]
[PXDBCalced(typeof(Add<PX.Data.BQL.Substring<GLTran.finPeriodID, int5, int2>, PX.Data.BQL.Substring<GLTran.finPeriodID, int1, int4>>), typeof(String))]
[PXUIField(DisplayName = "Period ID")]
public virtual String FinPeriodID { get; set; }
public abstract class finPeriodID : BqlString.Field<finPeriodID> { }
#endregion