Hi!
I'm not into the topic but one think paid my attention. Of course, after every import you should change ID's on target enviroment but you can use process const. or global const.
In different way, maybe better will be use column from DB based on GUID ex. DTYPE_GUID?
Guid's are the same in every environment in the process so maybe it will help with changing ID's everytime.
@Katarzyna
Maybe I don't understand your case and I'm completely wrong.
What I understand is the following:
- You have a report which shows fields from the workflow and one item list. So the field values are repeated for each row in the item list for a given report.
- You want to create the sum of fields from another item list in another workflow instance
- This workflow instance is identified by the column Det_Att23 in the report and the WFD_AttChoose55 field in the workflow instance.
If this is true, I have no idea, how you could make this work.
This is a part from the executed SQL statement
FROM V_WFElements as wfelems /*TASKDETAILSJOIN*/ .... LEFT JOIN WFElementDetails on
There's no alias for the WFElementDetails which in turn will means that the Det_Att23 will be ambigues.
@Cezary
Do we have the option to select constants in reports? I did create an SQL function to return the value of a constant by it's Guid in the past to go around this problem.
I've also added the user voice to extend the V_WfElements with the GUIDs because of the issue you mentioned. Using Guids in calculated columns means additional work on the SQL server.
https://community.webcon.com/forum/thread/4134?messageid=4134
Best regards,
Daniel