-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mashups being added to the wrong projects leading to false imports #60
Comments
Hi @Frowne, |
That's basically how it plays out - I would only commit after exporting Project X with all things once, then swapping to Project Y and exporting all of those, which is probably why they are all jumbled up. So just so I understand you correctly - the only way to correct this now is to delete the files from the repository, push that & then be more careful in the future? Also, I'm not sure I'm following on the "correct" commit procedure - do I:
Thank you so much for your help! I genuinely appreciate it. |
Actually, upon re-reading I think I misunderstood - no, the entities always belonged to Project X or Project Y respectively, that never changed - I only exported them through the Git Main Mashup! |
@Frowne
|
@Frowne just to be sure, are you using 5.0.0 or 5.0.1 ? |
@vrosu I've been using 5.0.0 as stated above - hence why I mentioned upgrading to 5.0.1 potentially! So the current procedure would be to clean up the working index within the workspace tab, but now I'm confused about an earlier thing - is it not enough then to just "be careful" with the exports to make sure you're not exporting duplicates? Feels like it could be a bit of a hassle if I have to constantly fix the working index... Or would that just be necessary if I do export poorly? Ultimately I think the main thing that I didn't realize is that I should be clearing out the window on the right from the screenshot above after selecting the second project to export and that pushed things into the wrong project potentially, does that sound about right? So before commiting future stuff, I clean up the working index, commit that (probably delete the local repo on the receiving end) and then just export the projects one by one making sure there's no overlap in the right hand window during export. Again, thank you so much for your help! It's much appreciated. |
Good day,
We've been using the extension for a while and have been super happy with it up until now - the last time we pushed a patch however, I noticed that some files appeared out of date. Checking the repository revealed that there are two folders for each of the projects, let's call them Project A and Project B.
Project A should only consist of three Mashups and no other things, while Project B holds a bulk of our working environment. The problem is, that a huge chunk of Things and Mashups exist on both of them with different last updated times.
Since the latest Thingworx / Extension update, we always import the full path and my best guess is, if a Thing's updated version is only in Project A, then it will be overwritten by the old version in Project B, which leads to the problem mentioned above.
Here's my question then - are we using the Extension wrong or is there an underlying problem? The way our export process works is as follows:
When exporting Project B like this, we do see the list of files that were in project A, but I assumed since we selected the project, it wouldn't be exported into the folder the project doesn't belong to, which might be wrong - it might also be the include dependents that's causing issues, but I would love some insight on the matter so we can either do it properly in the future or shed light on an existing issue.
Best regards!
Frowne
The text was updated successfully, but these errors were encountered: