[Question]: CICD is getting a license file error without using any secret related to the License file

[ismailhafid1]

Question

our CICDs was generating builds perfectly for a specific repository , but we created a simple test method in our testing app that uses WorkDate() , and based on some research i found out that workdate by default uses the latest G/L Entry posting date if the license is a demo, however our CICDs doesn't use any specific license file , now the main issue is that after building the app , the test with workdate that we created breaks the CICD because he find that the workdate is outside of the range of the license file Dates :

• error for Field: Posting Date, Message = 'In the current company the date you've entered is outside the allowed interval (this is determined by the filter '??11|??12|??01*|??02*', which is defined by the license file). (Select Refresh to discard errors)**

(the test works fine in a local environnement because we have the control over the work date and the license).
even if i try to specify a date in the Posting date (Ex: Today), the CICD returns this error because the workdate is already defined by the system :

• Function Update Shipment Date with Posting Date Unhandled UI: Message Shipment Date 03/05/25 is before work date 06/04/25

i can't find a way to bypass this problem without deleting the test from the test app.
My Question is :
Which License is the environnement is using if i m not specifying any secret with a License ? and how can i bypass or correct this error ?
logs_35227003032.zip

[ismailhafid1]

@freddydk any news about this issue ? i tried everything to make changes for the workdate , i even used some AL functions to get the license dates , add one day and assign this value to workdate , but it is always the same error

[freddydk]

You should be able to create a secret called LicenseFileUrl (found out that this isn't documented on https://aka.ms/algosecrets - will do), pointing to a direct download URL to your license file.
Then your license file will be used for CI/CD - that is the only way you will get this to work, I think

[freddydk]

This PR: #1620 adds the description to secrets docs.

[ismailhafid1]

Thanks, it worked