Custom Lookup fields loose data references when moved to another instance
<>
Hi All,
Facing this issue whenever we add a custom lookup field (could have/not have default value) in our dev instance and deploy it as package to Test instance. The section objects restricts the creation of record and thus throwing this error message as attached here. Once we re-publish the object, the data reference error is no more. But ideally when we move any package from dev to QA, this publish is literally adding few schemas to the folder which is not the correct way.
An additional observation is this occurs only when we receive "DataStreamError" while updating package from SourceTree.
So kindly suggest on how to handle this.
We use SourceTree and Azure Devops Repositoy to push our code.
Package version - 7.18.0.1350_SalesEnterprise_Marketing_ServiceEnterprise_Linux_Softkey_PostgreSQL_ENU_NetCore.zip
Platform - DotNetCore
Database - PostGres
OS - Windows
Appreciate your input.
Thanks
Anupama
Like
Hi Anupama,
DataStreamError can be a result of a connection loss between the app and repository and as a result not all the changes are being transferred. Can you please specify what happens if you export the package from the dev-app and import it to the target app using standard package export\import?
Best regards,
Oscar
Anupama,
Please provide us with the detailed step-by-step instruction on how can we reproduce the same issue in the local app and we will check it.
Best regards,
Oscar
Oscar Dylan,
It is reproducible in two scenarios:
- When we deploy and update package in a new instance/environment-
- we use Git and SourceTree for source control. when we clone the repository and update the package, we get the attached error<StreamError.jpg>.
- we use Git and SourceTree for source control. when we clone the repository and update the package, we get the attached error<StreamError.jpg>.
- While installing any marketplace plugin in existing instance
- installation fails and in the error log the same error message is captured
<<uploaded the error logs in the main section>>
- installation fails and in the error log the same error message is captured