• State Suggested Answer
  • Replies 40 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 2785 views
  • Users 0 members are here
Options
Related

Odd template behavior in 9.3

henrik a johansson
3 months ago

I have a template for UNSAccountB and when I create an account manually the template works fine, but when I do it using a business role it doesn't work.

This is the relevant portion of the template (they are identical between FullManaged and Unmanaged):

Else
	Dim CentralAccount As String = $FK(UID_Person).CentralAccount$

	If $FK(UID_Person).CCC_ImportSource$ = "ACME" Then
		CentralAccount = CentralAccount.Substring(0, CentralAccount.Length - 4)
	End If

	Value = CentralAccount
End If

Parents
  • 0 3 months ago

    I take it the BR assigns the account definition, right?

    I've made some tests and it works fine in my case.

    • Modified the template for the CN attr on a custom UnsAccountB
    • Created the UNSAccountB and linked a user. The template works.
    • or, located the user in Manager, assigned the corresponding account definition and the template applied, too

  • 0 3 months ago in reply to juancarlos camargo

    There's more to it, Markus. 

    The info you requested:

    PS C:\> dotnet --list-runtimes
    Microsoft.AspNetCore.App 8.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
    Microsoft.AspNetCore.App 9.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
    Microsoft.NETCore.App 8.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
    Microsoft.NETCore.App 9.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
    Microsoft.WindowsDesktop.App 8.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    PS C:\> dotnet --list-sdks
    8.0.404 [C:\Program Files\dotnet\sdk]
    PS C:\>

    The other machine is linux and it's running the jobserver and dbagent on docker containers.

    It's been a temporay success. The problem persists. Only worked once after:

    • Changing the jobserver and dbagent
    • Resetting the administration workstation (the one I've ran the dotnet --list-runtimes)

    Now it's there again. The jobserver and dbagent keep running on docker. But I've made changes to the UNSAccountB template and renamed the process. Recompiled the database and , again, the template that's applied is the older one from early this morning and the process name shown in jobqueueinfo keeps being the older one too.

    I've changed the Designer settings:

    * Save databases locally:OFF

    * Use RAM: ON

    * Clear caches

    reopened Designer. Tried and, again, no changes at all. Template does not apply, process keeps the older name.

    Changed the administration workstation, retried. Nothing. The template does not apply, process keeps the older name, though I've changed it 2 times and recompiled the db.

  • 0 3 months ago in reply to juancarlos camargo

    In your case, the JobServer is running in a Linux Docker container, right? If you delete and re-create the Docker Container (just stopping and starting is not enough), does it work then (assuming that you do not persist the caches)?

  • 0 3 months ago in reply to Markus Weiss-Ehlers

    YES!!!! (I cannot attach images)

    It works!!! Recreated the container and now I can see the job process name has been updated in jobqueueinfo and the template is applied correctly.

    Changed the process name again, retried and it keeps being the older one. Recreated the container. Process name updated. 

    Yes, you've found it  100

Reply Children