Installing fonts into the container build action.

[FMDSimon]

We are depending on a 3rd party app from Yaveon. Currently the workflow fails on app "Yaveon 365 Process Base", however we are not certain that the other apps would succeed, as they are not attempted.

The error we encounter is "Invalid font family: the font 'Segoe UI' is not installed"

Yaveon support has provided us with the attached code (See "Yaveon install fonts.txt") to resolve the issue, but we have not been able to implement the fix in the workflow.

We have tried to incorporate installing fonts into several different points in the build step as we assume the BC container must be created and running before installing the fonts.

We have not been able to add this code without running into other errors.

Can you assist in adding these fonts to the BC container?

Error:
Unexpected error when running action. Error Message: Could not install the extension 'Yaveon 365 Process Base' by 'YAVEON GMBH' (version '11.4.99.0') on tenant 'default' and company 'CRONUS Danmark A/S' due to the following error:
'Errors were detected in the RDLC layout:
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.
Invalid font family: the font 'Segoe UI' is not installed.

Workflow run: https://github.com/FellowmindBCDK/Crispyfood/actions/runs/19026805487

Yaveon install fonts.txt
_BuildALGoProject (1).yaml
logs_48985453148.zip

[aholstrup1]

If you haven't tried this already I would try adding a NewBcContainer.ps1 override in your build (See docs here:
https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md#run-alpipeline-script-override)

That way you can add the fonts during the build just after the container has been created. If this doesn't work you might need to get further help from Yaveon support

Param(
    [Hashtable]$parameters
)

# Create container 
New-BcContainer @parameters

# Add fonts 
$fontsToInstall = @(
            'C:\Windows\Fonts\arial*',
            'C:\Windows\Fonts\calibri*',
            'C:\Windows\Fonts\cambria*',
            'C:\Windows\Fonts\consol*',
            'C:\Windows\Fonts\cour*',
            'C:\Windows\Fonts\fram*',
            'C:\Windows\Fonts\lucon.ttf',
            'C:\Windows\Fonts\micross.ttf',
            'C:\Windows\Fonts\Roboto*',
            'C:\Windows\Fonts\seg*',
            'C:\Windows\Fonts\tahoma*',
            'C:\Windows\Fonts\times*',
            'C:\Windows\Fonts\trebuc*',
            'C:\Windows\Fonts\verdana*',
            'C:\Windows\Fonts\webdings*',
            'C:\Windows\Fonts\wingdings*'
        )
 
Add-FontsToBcContainer `
            -containerName $containername `
            -path $fontsToInstall
 
Restart-BcContainerServiceTier -containerName $ContainerName

[aholstrup1]

The commit you were on when you took the screenshot (bce66e7) comes from the same test branch that you were running the CI/CDs on?

The log you shared yesterday ran on commit af2e9340983f589fe943b60f931658e73ad4c1a1 - Any chance you could share the same screenshot from that commit? Does it have the same file structure?
@MortenStavad

[FreundDK]

SÅ dvs. når du kører CI/CD manuelt - så vælger du branch her:

Eller hvad?

[MortenStavad]

@aholstrup1
On commit af2e9340983f589fe943b60f931658e73ad4c1a1 is after we removed the override in the settings and precompile app since we could not get to work we went back to standard

@freddydk
Ja det er korrekt. Vi kører vores Workflowtestpart2.0

[FreundDK]

Det er svært at pin-pointe hvor det helt nøjagtigt går galt - men i gør det rigtige.
Filen skal hedde NewBcContainer.ps1 og placeres i .AL-Go folderen.
Der skal ikke være nogen settings.
Hvis i har lyst, kan jeg godt hoppe på et 30 minutters teams kald og kigge på jeres pipeline sammen med dig.
Smid en mail til fkr at freddy.dk hvis vi skal finde ud af det - det skal ikke koste jer noget.

Jeg kan også foretage et egentlig review af jeres AL-Go (for optimeringer mm) - det er naturligvis ikke gratis nu hvor jeg ikke er i MS:-)

[freddydk]

I tried to make a repro of this here: https://github.com/[Freddy-DK/overridetest](https://github.com/Freddy-DK/overridetest)

That seems to work just fine - I even tried to create another branch and place the NewBcContainer in that (and not in main) - still works.
In the build log, you can see the override printed out:

and during execution (container creation), the script is running:

I don't know why it isn't working at your place, but I would put the blame on the changes you make to some of the pipelines earlier - probably.

[FreundDK]

In the meantime, I found out what probably was happening here.
The overrides used by AL-Go - if they contain a syntax error or like, they will just be ignored, the override will just not be included.
So any small mistake in the script causes a silent failure - which is not what we want.
I have included a fix for this in a PR.