Skip to main content

Imagine you have a Project and make a full Export from your Development Environment.

Now you import it into your Test or Production Environment.


Why do I have to care about to delete all ENTITIES in this Project-Export-File before importing it???

Why does Uniface not make this Job?

If I rename a Field from OLD_FIELD to NEW_FIELD than I have both Fields after the import in my Entity and the Program will no longer run, as there are Differences between Model and Database.


Is there a switch to set when importing?


Regards

Norbert

Imagine you have a Project and make a full Export from your Development Environment.

Now you import it into your Test or Production Environment.


Why do I have to care about to delete all ENTITIES in this Project-Export-File before importing it???

Why does Uniface not make this Job?

If I rename a Field from OLD_FIELD to NEW_FIELD than I have both Fields after the import in my Entity and the Program will no longer run, as there are Differences between Model and Database.


Is there a switch to set when importing?


Regards

Norbert

The import function has ALWAYS had this issue (or at least since before Verison 8), which is why it is hard to use version control on the model. 

Fields which have the same name are pretty reliably overwritten, but deletions are not carried in the import, so the field is left untouched. 

If there is a switch, I'd love to know about it, but I don't think there is. 


Iain

Imagine you have a Project and make a full Export from your Development Environment.

Now you import it into your Test or Production Environment.


Why do I have to care about to delete all ENTITIES in this Project-Export-File before importing it???

Why does Uniface not make this Job?

If I rename a Field from OLD_FIELD to NEW_FIELD than I have both Fields after the import in my Entity and the Program will no longer run, as there are Differences between Model and Database.


Is there a switch to set when importing?


Regards

Norbert

We found that very annoying too, many years ago... We decided to build our own version control interface. We used an import function that deleted the object from the repository before importing the new version. We had that in Uniface 8 and 9 (with the additional menu). And used it many years. That made our version control very simple.  In Uniface10 we use a function we have written for the user defined menu.

In Uniface 8 and 9 we had to dive a bit into the less documented area 🙂 . Since Uniface 10 the meta model is well documented, so that was easy.

I believe there will be an open source solution on Github very soon. Just a couple of days. With that solution you can sync xml export files with your local repository. But since it is open source, you can take the contents and embed in your own development toolset!

Terms & ConditionsAccessibility statement