I was USING ISWE import export tool I wanted to import a program stage for specific TEI without creating a new one, I tried Importing it without filling TIE _ enrollment but it will push an error saying that its blank and I tried filling the same TEI ID i created inside the TEI_ID section but it rejected that and created a new one. i just wanted to fill one stage from
Hi @ButwhyRex
You mean it created a new tracked entitiy instance? I don’t know why it would do that… maybe it’s importing the entire TEIs and program stages instead of “updating”? Is there a setting to select ‘update’?
I’d have used the API but I haven’t used this app ISWE… would you like to share more about the usecase itself?
Importing program stages values into an already existing TEIs, did you try the import/export app? 
i haven’t tried the import export app, the main usecase of the iswe app as far as I understand, it will give you a downloadable template, you fill that template based on your desire and you will then import your data using that same template the app gives you,
yes I wanted to import the whole TEI itself but i have filled so much stages inside the current TEI and i don’t want to repeat that everytime something new comes to be entered in the stages,
I will check if there is an update feature , would you mind sharing how you used API to import thank you very much!
Hi @ButwhyRex and @Gassim,
I’m also interested in this use case, especially when working with Tracker data where a TEI already exists and we only need to add or update data for a specific program stage.
As I understand it, the key requirement is to identify the existing TEI and enrollment correctly, rather than allowing the import process to create a new TEI. For example, if the TEI already has several completed program stages, we should be able to import a new stage/event without having to recreate or re-import the previous stages.
I’m curious about the exact behavior of ISWE in this case. Does the template require both the TEI_ID and the enrollment UID for an existing enrollment? And if so, does ISWE currently support updating an existing TEI/enrollment, or does it always treat the import as a new TEI?
The API approach could potentially solve this by first identifying the existing TEI/enrollment and then creating or updating only the required event/program stage.
If anyone has a working example of the API payload or the correct ISWE template structure for this scenario, I’d be very interested in seeing it.
Thanks for raising this — this is a very practical Tracker data-management use case.
as far as I know the ISWE forces you to fill Enrollment + TEI ID otherwise it will throw errors while Importing,