Jana.safferova v 30. 8. 2022, 14:55

2022-08-30T14:55:17Z

← Starší verze		Verze z 30. 8. 2022, 14:55
Řádek 1:		Řádek 1:
	<languages />		<languages />
	First, we specify the identifiers for processing, in this case clientdepo1 and clientdepo2		First, we specify the identifiers for processing, in this case clientdepo1 and clientdepo2

Jana.safferova: založena nová stránka s textem „`$SOLVEDATE = ((get-date).AddDays($DAYOFFSET)).ToString("yyyy-MM-dd")`
`$SAVESTAMP = "C:\SFTPImport\EXP_TASHA_DAY_"`
`$SAVESTAMP = $SAVESTAMP+$SOLVEDATE+$FORMAT`
“

2022-08-18T07:53:04Z

založena nová stránka s textem „<code>$SOLVEDATE = ((get-date).AddDays($DAYOFFSET)).ToString("yyyy-MM-dd")</code> <code>$SAVESTAMP = "C:\SFTPImport\EXP_TASHA_DAY_"</code> <code>$SAVESTAMP = $SAVESTAMP+$SOLVEDATE+$FORMAT</code> “

Nová stránka

<languages />
First, we specify the identifiers for processing, in this case clientdepo1 and clientdepo2

<code> $DBNAMES = @("clientdepo1", "clientdepo2")</code> 

Determine the number of days from the start date of the statistics to today's date. Can be found at e.g. https://kolikdni.3tecky.cz/

''In this example, we will count 330 days, which will be entered as negative because they are days in the past.''

<code>$DAYSBACK = -330</code> 

Determine the input file format

<code>$FORMAT = ".csv"</code> 

We can set the level of message output, see. [[TAS:Pokročilé/Pluginy/TashaCL_-_příkazová_řádka/Možnosti_příkazové_řádky/en|Command line options]]

<code>$LOGLEVEL = 1</code> 

We can use the command '''cls''' '''' to clear the command line

<code>cls</code> 

Then we create a cycle that will iterate from the value that determines the number of days until the beginning of the statistics to 0 that determines today's day. For the 1st iteration in our example, we set '''$DAYOFFSET =''' - 330

<code>For ($DAYOFFSET=$DAYSBACK; $DAYOFFSET -le 0; $DAYOFFSET++)</code> 

In our case, the customer data is named for example EXP_TASHA_2019_02_20.csv, so the input format is .csv and we need to get the planning date in the appropriate format yyyy-MM-dd and the beginning of the name, which we set statically. Then we get the full address of the file and store it in the '''$SAVESTAMP''' variable

<code>$SOLVEDATE = ((get-date).AddDays($DAYOFFSET)).ToString("yyyy-MM-dd")</code> 
<code>$SAVESTAMP = "C:\SFTPImport\EXP_TASHA_DAY_"</code> 
<code>$SAVESTAMP = $SAVESTAMP+$SOLVEDATE+$FORMAT</code> 

For Tasha you also need to get the planning date in the format dd.MM.yyyy, e.g. 20.02.2019.

<code>$PLANNINGDATE = ((get-date).AddDays($DAYOFFSET)).ToString("dd.MM.yyyy")</code> 

Sets the location of the parent folder to the folder that contains Tasha_CL.exe

<code>Set-Location -Path "C:\CL_folder"</code> 

Create a cycle that iterates through all DBs contained in '''$DBNAMES'''.

<code>ForEach ($DBNAME In $DBNAMES)</code> 

Chaining can be used to list the information by writing the variable to a string.

<code>"Database: $DBNAME - Scenario name: $SOLVEDATE - Planning date: $PLANNINGDATE"</code> 
<code>"Import"</code> 

Start the import using the necessary variables, e.g. '''$DBNAME, $LOGLEVEL, $SOLVEDATE, $SAVESTAMP, $PLANNINGDATE.'''

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode import --PluginName SolverTech.Tasha.Plugins.IO.Tasha </code> 
<code>--inputscenarioname $SOLVEDATE --ImportFile $SAVESTAMP --PlanningDate $PLANNINGDATE </code> 
<code>--PluginSettings "C:\CL_folder\TashaCL\Plugins\IMPORTERSETTINGS\$DBNAME.config" </code> 

By default, the import, geocoding and distance calculation is performed within the previous command.

But they can also be run individually using the following commands:

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode geocoding --PluginName SolverTech.Tasha.Plugins.Geocoding.Ruian </code> 
<code>--inputscenarioname $SOLVEDATE</code> 

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode distance --PluginName SolverTech.Tasha.Plugins.UpdateDistance.Here </code> 
<code>--inputscenarioname $SOLVEDATE </code> 

Continue by running the solution using the necessary variables, e.g. '''$DBNAME, $LOGLEVEL, $SOLVEDATE'''

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode solve --inputscenarioname $SOLVEDATE -i30000 -tMediumHigh -z10 -ay --MaxProcessorCount 20 --RestartPhasesCount 5 --RestartPhasesPercentage 50</code> 

We then import the vehicle tracking data using the necessary variables.

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode command --PluginName SolverTech.Tasha.Plugins.Tracking.Webdispecink --CommandName UpdateTrackingDistances </code> 
<code>--inputscenarioname $SOLVEDATE --TrackingCompany Company --TrackingLogin Name --TrackingPassword Heslo1111</code> 

Make an input to the KPI database.

<code>TashaCL\TashaCl.exe -s SQLServer -c "SERVER = TS3\SQLEXPRESS; DATABASE = $DBNAME;Integrated Security=SSPI;" </code> 
<code>--logginglevel $LOGLEVEL --Mode command --PluginName SolverTech.Tasha.Plugins.Statistics.Kpi --PluginSettings "C:\CL_folder\TashaCL\Plugins\KPISETTINGS\$DBNAME.config" --CommandName UpdateKPIs</code>

TAS:Pokročilé/Pluginy/TashaCL - příkazová řádka/Automatický update KPI statistik/en - Historie editací

Jana.safferova v 30. 8. 2022, 14:55

Jana.safferova: založena nová stránka s textem „$SOLVEDATE = ((get-date).AddDays($DAYOFFSET)).ToString("yyyy-MM-dd") $SAVESTAMP = "C:\SFTPImport\EXP_TASHA_DAY_" $SAVESTAMP = $SAVESTAMP+$SOLVEDATE+$FORMAT“

Jana.safferova: založena nová stránka s textem „`$SOLVEDATE = ((get-date).AddDays($DAYOFFSET)).ToString("yyyy-MM-dd")`
`$SAVESTAMP = "C:\SFTPImport\EXP_TASHA_DAY_"`
`$SAVESTAMP = $SAVESTAMP+$SOLVEDATE+$FORMAT`
“