-
Notifications
You must be signed in to change notification settings - Fork 1
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
How to migrate files, photos and Email Templates? #2
Comments
It was not the intention of this project. Email template I'm guessing is just the HTML you need to copy and place in Sashido's cloud code. They have help blog guides. For images... that took a while. Basically I have to run a script that downloaded and re-uploaded to Sashido. |
thanks for the response. I have another problem. In arrowdb I have some field names with spaces like "first name", now while migration, it gives me did not go through! => { |
How were you able to create property names with spaces in Axway? I wasn't aware that was possible. Given Axway will be shutting down end of this month. I suggest you download the DB from Axway before the end of the month as a back up. |
New release 0.2.1 that will remove the spaces from the keys. Also Relations are now Pointers, which will be easier to fetch when Querying Sashido, since it will return the Query and the |
Wow, great. I will check this. Not sure this will also fill the creator user. I had filled users first before creating custom objects, but was getting creator as follows: |
I think you can also look into the below error: This happens when axway username is not defined in user table. In axway username is optional if email, firstname and lastname are filled. Is it possible to migrate and fill email in username if username is not defined? |
I downloaded 0.2.1 and tried importing object, its creating object but skipped all field name with spaces, just created one field { |
Could you please let me know the steps/process to migrate files, photos and Email Templates?
The text was updated successfully, but these errors were encountered: