Adding test data using data service returns null when executed

Feedback Test Cloud
,
1

While Debugging or running from the design mode it is throwing object reference error when we add test data using data service. It only works fine when we run from test explorer or publish it to the orchestrator.

3

Possible Reasons Why It’s Not Working in Design/Debug Mode:*

*Configuration: Misconfigured Data Service settings or missing information in your local environment.
*Environment Variables: Data Service might need variables that are only set up correctly in Orchestrator/Test Explorer.
*Permissions: Your local debugging setup might lack permissions the Data Service needs.
*Connectivity: Network issues preventing your workflow from reaching the Data Service locally.

Troubleshooting Steps:

  1. Test the Data Service Alone: Create a simple workflow just to test the connection and data retrieval from the Data Service.
  2. Check Your Settings: Double-check the Data Service’s configuration in your workflow (URLs, API keys, etc.).
  3. Look for Environment Variables: Does the Data Service need variables that are only configured in Orchestrator/Test Explorer?
  4. Read Logs/Errors: Examine error messages for clues about what’s going wrong during debugging.
1 Like
4

Hi @srinivasmarneni

When I tried to get the data using data service activities ,I am able to get the result

image
image760×331 9.27 KB

So I don’t think this is an issue with the settings or configuration

Thanks
Lakshmi

5

Given that you are able to retrieve results using Data Service activities, the issue might be related to the context in which the activity is executed. Here are some steps you can take to troubleshoot the issue:

  1. Initialization*: Ensure that any variable or object used within the ‘Query Entity Records’ activity is properly initialized before use.
  2. Contextual Differences*: There might be differences in the environment context between design time, test execution, and published processes. Check if there are any dependencies or variables that are being set differently across these contexts.
    3.Activity Properties*: Double-check the properties of the ‘Query Entity Records’ activity to ensure that all required fields are populated and that the activity is configured correctly.
    4.Error Handling* : Implement error handling around the ‘Query Entity Records’ activity to catch any exceptions and log detailed error messages. This can help identify what is causing the null reference.
1 Like
6

Hi @srinivasmarneni

Query Entity records activity is working fine only. I am facing issue while adding my service as test data .It is getting added successfully but facing issue while running from design panel. The execution is working fine when running from test explorer or when the test case is published to orchestrator.

Thanks,
Lakshmi

7

you encounter an issue when adding the data as test data during the design phase. This issue does not occur when running tests from the Test Explorer or after publishing to Orchestrator.

This suggests that the problem might be related to how the data is being initialized or handled in the design environment versus the test or published environment.

  1. Ensure Initialization*: Confirm all variables and data services entities are initialized before use.
  2. Error Handling*: Add error handling to capture detailed information during the design phase.
  3. Consistency Check*: Compare environment settings between design-time, Test Explorer, and Orchestrator to spot differences.
  4. Log and Debug*: Use logs and debug mode to identify at what point the null reference occurs.
  5. Version Check*: Ensure all dependencies are consistent across environments.
8

Hello @srinivasmarneni ,

thx a lot for the feedback, we can reproduce the behaviour and have created a logged a bug in our system.
We will try to fix the issue as soon as possible.

BR
Thomas

1 Like