PTC task management integration

medini_1052758087

Hello Jan, We have a query from one of the customers, please see below:  In their Installation of PTC, the Field definition is deviating from PTC- (former MKS-) Standard ( please refer screenshots) PTC : The basic setup has been done by an consultant, using DB-Fieldname “Projekt” for the IM-Projectfield, Type “project”. At a former update they notified trouble in certain Views of the local PTC Client, cause PTC have done an Update using (hard-coded !!) the Fieldname “Project” (like PTC Tool-Default) instead of logical Link to Project Field. For that Reason the customer created in addition a Dummy Field “Project” to be able to use that View. we tried to change the mapping field  from  -> PTC Side: "Projekt"  -> medini side: "task.common.product" But still it doesn't work. Changing the mapping doesn't work and they doubt if in our interface we are using (also hard-coded) the Field “Project”.  What happens is if the mapping is changed, the field Project is changed to Projekt but there is no dropdown menu available and it throws an error there are some missing fields even though these are filled. Please see the below screenshot: Thanks and regards, Smitta 

medini_1024169437

Hi Smitta, it seems that not the Project/Projekt mapping is the problem, but yet another mandatory field named "Planned target date". Seems it is mandatory and not mapped. The date in the "Private" section (Scheduled, Due, Estimate) are really *private* data and only stored per user in the workspace, they are not mapped. So you need to map the remote PTC field to something on the medini side. Maybe you first need to find out what kind of mandatory dates you have? Please also attach always the mapping file in this kid of questions. Jan