I have already tested enabling debugger and break on triggers also, but it doesn't go through any code. Not even to reach cu1 yet...
Maybe it is on the domain controler and the authentication, because I can login with database authentication or it is in the extended stored procedures...
I have notified the IT dept to check the domain and the in general if there is an error there...
If you're seeking how to remove password protection from PDF, use SysTools strongly encrypted PDF password remover tool, one of the advanced solution for removing the security. This amazing tool deals with all kind of PDF restriction or password encryption. It allows you to remove restrictions like editing, text copying, password, printing, and commenting. So, remove password from secured PDF in bulk mode. Download this tool on your Windows or Mac OS.
Hello kristiela, if you pay close attention to the No. Series Code (first column to the left), you will see they are not the same.
On the first screenshot, where you opened it from the 3 dots (...), it's pointing to No. Series "SP"
On the second screenshot, where you have a blue circle, it's pointing to No. Series "EX"
On the Second screenshot you would need to look for the SP one to flag it correctly, or you could also just hit "Edit List" from the first screenshot so that you can edit the number series SP right there and then.
This should be fairly easy with a Table Extension on the Sales Header table, however I tried it myself and it didn't seem to work.
The contents of tiles are controlled by fields on fieldgroup Brick, defined on the Table. The Sales Header table already has 5 fields defined on the Brick fieldgroup. I tried adding a Table Extension to add the Shipment Date to the Brick fieldgroup and it simply didn't work.
This is standard behaviour.
At startup, the development environment looks for a local fin.flf file in client directory,
before it falls back on the server license.
Somebody renamed a development license to fin.flf, and put it in the client directory.
It is even possible to look for license files at other places. Check the shortcut properties of the dev environment for that.
This explains why the client is running fine.
They both run under a different license at start.