Error: Input Dialog: TypeConverter cannot convert

[DJOBBI_Oussama]

Hello everybody,

I have a problem, we have an rpa which works very well for others but for me, it sends me the error Error: Input Dialog: TypeConverter cannot convert

la configuration est la suivante c’est simple, get text / scarping method = target anchorable / output excel cell.

any idea from or suggestion please ?

[rodrigo.simao]

Hello @DJOBBI_Oussama, try this:

1. Review Input Dialog Activity: Double-check if there’s an Input Dialog activity in your workflow. The error message you provided seems related to Input Dialog, so ensure that this activity is correctly configured, and there are no data type mismatches in the input parameters.
2. Check Get Text and Scraping: If the core of your process involves “Get Text” and scraping methods, the error might not be directly related to an Input Dialog. Review the configurations of these activities, and make sure they are correctly extracting and processing data. Check if any of the scraped data needs to be converted before using it in an Input Dialog.
3. Data Conversion: If you are passing data from the scraping activities to an Input Dialog, ensure that the data types match the expected input of the Input Dialog. For example, if you are trying to input a string into the Input Dialog, make sure the variable or value you’re passing is indeed a string.
4. Debugging: Use UiPath’s debugging tools to step through your workflow and identify the exact point where the error occurs. This will help you pinpoint the source of the issue.
5. Variable Types: Check the data types of any variables or arguments used in your workflow. Ensure that the data types match the expected types for the Input Dialog.
6. Logging: Implement logging throughout your workflow to capture variable values and debug information. This will assist you in identifying the specific data causing the error.
7. UI Changes: Ensure that there haven’t been any changes in the application’s UI or layout that might be affecting the scraping activities.
8. UiPath Version: Check if you and your colleagues are using the same version of UiPath. Sometimes, differences in UiPath versions can lead to compatibility issues.
9. User Permissions: Ensure that you have the necessary permissions to run the workflow, access the application, and interact with the UI elements.

Cheers!

[supermanPunch (Arpan)]

@DJOBBI_Oussama

it sends me the error Error: Input Dialog: TypeConverter cannot convert

Hi @DJOBBI_Oussama ,

Could you let us know which activity is producing this Error ?

We have encountered this when the type of value retrieved from the activity does not suit the Output variable type used.

So, changing the variable type to UiPath.Core.GenericValue was helping us to prevent this error. We can then convert to the required type by assigning it to another variable.

But do let us some more details before performing a change, so that we can conclude the changes to be done.

Some posts having similar issues :

InputDialog: TypeConverter cannot convert from System.String

I very much appreciate your response. This lead me find to what I believe to be a good solution, though it would be nice if the activity itself would do the conversion for me based on the value of IsPassword. I also chose to mark the activity as private to avoid outputing plain text passwords in the log data. new NetworkCredential("", password ).SecurePassword [image] [image]

[DJOBBI_Oussama]

Thank you very much for your quick replies

the activity is get text “engine cycles” to copy it into an excel field

[DJOBBI_Oussama]

[Nitya1 (Nitya Tomar)]

Hi @DJOBBI_Oussama

The error message “Error: Input Dialog: TypeConverter cannot convert” suggests that there’s an issue with the data conversion or data type being used in your Input Dialog activity. It’s not directly related to the “get text,” “scraping method,” or writing to an Excel cell activities.

Here are a few steps to help you troubleshoot and potentially resolve this issue:

1. Input Dialog Activity: Verify the Input Dialog activity’s properties, especially the data type expected for the input. Make sure the data type you’re trying to input matches the data type expected by the Input Dialog. It’s possible that the Input Dialog is configured to receive a certain data type, and you’re providing a different one.

2. Data Conversion: If you need to convert data before displaying it in the Input Dialog, make sure that the conversion is done correctly. For example, if you’re trying to display a number, ensure that you convert it to a string using the appropriate conversion method or expression.

3. Check the Input Value: Review the specific input value that you’re trying to pass to the Input Dialog. It could be a variable or an expression. Make sure this value is valid and of the expected data type.

4. Testing: Try testing the Input Dialog activity with simple values to see if the error persists. Start with a hardcoded value to see if the issue is related to the specific data you’re trying to input.

5. Debugging: Use UiPath’s debugging tools to step through your workflow and see where the error occurs. This can help you pinpoint the exact activity or step that’s causing the problem.

6. Log Information: Add logging activities in your workflow to capture the values of variables or expressions before they are used in the Input Dialog. This can help you identify any unexpected data.

7. Version and Environment: Ensure that you are using the same version of UiPath as others, and that your environment (e.g., Excel version) matches the one used by others who are not experiencing this issue.

Thanks!!