Problem with Log File

Hi ​@bernardocavalcante,

In A360, when you read a JSON into a Dictionary and want to reference its values:

• Use quotes around the key:

               p_dicConfig{"DIRETORIO_LOG"} - Correct
               not p_dicConfig{DIRETORIO_LOG} - Wrong

• Use the Windows path separator \ (or \\ inside JSON), not /.
• Ensure your JSON paths have escaped backslashes:

               "DIRETORIO_LOG": "C:\\RPA\\MeuBot\\Log",
               "NOME_ARQUIVO_LOG": "Bernardo.Log"

$p_dicConfig{"DIRETORIO_LOG"}$ + "\" + $p_dicConfig{"NOME_ARQUIVO_LOG"}$

• JSON keys have escaped backslashes:
• "DIRETORIO_LOG": "C:\\RPA\\MeuBot\\Log"
• Dictionary keys use quotes: {"KEY"}
• Use \ (not /) for Windows paths.

This will resolve the error.

Hi @Padmakumar, thank you for the guidance!

I followed your advice and added the quotes to the dictionary keys (e.g., $p_dicConfig{"KEY"}$). However, I am now facing a "Path not found" error specifically at Line 14 (inside the Catch block).

Looking at the error message (screenshot attached), it says: "Verify the file path '+'/' + ' and try again."

It seems like the bot is interpreting the + characters literally instead of performing a string concatenation.

Currently, my syntax in the "Log to File" path field is: $p_dicConfig{"DIRETORIO_LOG"}$ + "/" + $p_dicConfig{"NOME_ARQUIVO_LOG"}$

Should I remove the + operators and just place the variables next to each other (like $Var1$\$Var2$)? Or could this be an issue with the dictionary variable returning null?

 

The error message confirms the issue: A360 is treating + and / as literal text, not as concatenation. This happens because the Log to File action does not parse expressions—it expects a single resolved string.
 

Remove all + and / from the Log to File path field and build the full path in a String variable first.

String: Assign → sLogPath
sLogPath = $p_dicConfig{"DIRETORIO_LOG"}$ + "\" + $p_dicConfig{"NOME_ARQUIVO_LOG"}$

(Use \ for Windows paths.)

In Log to File, set File path to: $sLogPath$