Optima problem z importem e-zwolnień 2019
Optima 2019.1.1 problem z importem e-zwolnień
Podczas zaciągania zwolnienia z PUE w formacie csv program Optima pokazuje błąd:
Import z pliku e-Zwolnienia: czas wykonania: 00:00:00, błędów: 1,
Import nie jest możliwy - niepoprawny format pliku
Problem występuje wtedy gdy w pliku csv - w nazwie pojawią się cudzysłowy, które są traktowane jako znaki specjalne.
Problem można rozwiązać edytując plik csv i usuwając wszystkie cudzysłowy
9511998317,"""MALA-MED"" SP. Z O.O.",87122,Grebocin,DEKERTA,12,,1234666,KAROL,MONTON,2019-01-05,WYSTAWIONE
z tej linii należy wykasować wszystkie cudzysłowie
i zostawić w formie:
9511998317,MALA-MED SP. Z O.O.,87122,Grebocin,DEKERTA,12,,1234666,KAROL,MONTON,2019-01-05,WYSTAWIONE
How do I delete Shortcuts from All Users desktops?
If you're talking about the All Users desktop, it can be found here:
- Windows Server 2003: %ALLUSERSPROFILE%\Desktop
- Windows Server 2008 and above: %PUBLlC%\Desktop
If want to remove shortcuts from each user's desktop, then you could write a script that deletes all *.LNK files from %USERPROFILE%\Desktop, or where ever their Desktop is redirected to ( %HOMESHARE%\Desktop).
Another method
Step 1. Edit a GPO that targets the computers that you want to apply the home page setting.
Step 2. Navigate to User Configuration > Preferences > Control Panel Settings > Windows Settings
Step 3. Click on the “Action” menu and click on “New” and then click on “Shortcut”
Step 4. Change the Action to “Delete” then select “All Users Desktop” and then type “Adobe Reader 9” in the name field.
Error: The term 'test.ps1' is not recognized as the name of a cmdlet
Error
The term 'test.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
When running a script like ./Test.ps1
the script is expected to be in the current working directory (.
).
Depending on the environment from which you're executing that statement the working directory may not be what you expect, though.
Here are some commands that allow you to determine the current working directory when run the same way as your script:
$PWD.Path
(Get-Location).Path
(Resolve-Path '.').Path
There are basically 3 ways to deal with the issue:
- Specify the path to your PowerShell script relative to the current working directory.
-
Change the current working directory to the location of the PowerShell script:
Push-Location 'C:\temp\folder' .\Test.ps1 Pop-Location
-
Run the PowerShell script with its full path:
& 'C:\temp\folder\Test.ps1'
If the executable's filename, path, or pathname doesn't contain spaces, using the call (&) operator is optional. Otherwise, the call operator is required.