Parse.com exported data missing _Schema - parse-platform

Hi exported my app before parse.com was shutdown and I saw some JSONs so i though it is OK. Today I tried to import these data to mongo only to find out that I need _Schema file import too but it is missing from the exported file.
Is there a way how to generate this file?

Looking at the _SCHEMA collection of my local Parse Server installation it seems fairly easy to reconstruct manually. It only contains the columns and their types for each collection with the collection name being the object id.
Below is an example of the _SCHEMA entry for my _User collection

Related

How can I import a class from back4app, which contains images, into another back4app database?

I have a back4app parse database that has a class containing images. I need to import this class into another back4app parse database. When I export it to json and attempt to import it, I get the following: This XML file does not appear to have any style information associated with it. The document tree is shown below. Followed by an error stating access denied. What do I need to do to get this to work?
To clarify the solution: the files must be cloned into the new database, which can only be done by contacting back4app directly and asking them to do it.
I recommend that you sent a email or talk at chat with Back4App, the error that you reported is necessary clone your files/images.

How i can import data from parse.com service in my own a mongodb database?

As you know, parse.com will be closed.
I made export of all collections.
Now i have the many dumps of collections.
Collections name like:
_User
AppParentCompany
It's normal tables name, but between this files i have relations, a relation contained in the next file:
_Join:parentCompanies:_User.json
Latest file name i understand like:
_Join - is relations
parentCompany - it's column
_User - a collection containing parentCompany column
Based on this, i have next questions:
How i can import this relations into a database?
What name will be for this collection of relation?
Thanks!
Take a look at this page: https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App
Prepare mongodb database connection string first.
Go to Parse your project's App Settings > General.
Find App Management > Migrate to external database. Press Migrate button.
Enter your database connection string, it will start with mongodb://...
Then press Begin the migration.
Then Parse will do the rest for you.
P.S. If you are using mongolab, go the web browser, into your database, then you can find _Join:xxx:xxx,​​​​​​ _SCHEMA and more in Collections.

Parse.com: How do I create a clone of one App

We are collaborators on a Parse.com App and we need to recreate the App in another account as we are ending our relationship with the original App creators.
We have copied all the classes and exported all the data from the previous App but are getting errors with the JavaSript API (Access Denied/403 issue). Has anyone else experienced this? What did you do to overcome the problem?
Thanks!
The Parse.com dashboard has export to JSON which you can then import from the data browser on your second app.
Object IDs will not be preserved.
One big thing to be aware of:
Any referenced PFFiles are NOT exported, so all the references in your rows are not valid, as the new database is not part of the ACL of the old PFFiles.
Either export+import the PFFiles manually, or change the ACLs, if that is indeed possible.

Sample of how to create and save new entity, Breezejs

Im trying to create a very basic Todo-entity from the Breeze example.. Im doing:
manager.createEntity("Todo",{Description:"Test",Id:32,IsDone:false});
But I keep getting an error where the console tells me that it couldnt find the Type "Todo".. I have tried all types I can possibly think of..
Could anyone please provide me with an example of how to create an entity for the breeze WebApiSample.. cause this is driving me nuts..
Thanks alot!
Breeze needs metadata in order to create an entity of any type. That metadata can either be returned from the server or created locally. My guess is that you haven't yet done either of these. Metadata from the server is usually automatically fetched by Breeze during its first query against the server. Alternatively you can cause it to be fetched directly via the MetadataStore.fetchMetadata method.
Hope this helps.

Programatically retrieve an attachment stored on a note on a CRM 4.0 entity

How would you suggest working with files that is stored on the note of a entity in Crm. Could you write a generic method that will enable you to access any type of file? Or would it be better to have a method for dealing with each type of file?
For example, we are going to be saving a mix of swf files and xml files on the entity, so would it make sense to have a method each for example:
GetXmlFilesOnAccount(accountid)
GetSwfFilesOnAccount(accountid)
When you upload an attachment to CRM the mimetype is also saved as part of the record information.
The following link contains a nice example of how to download the attachemt using a single method. http://crmscape.blogspot.com/2009/10/ms-crm-40-sending-attachments-to.html
The post is missing the actual query needed to retrieve the annotations but you can tell what columns are required from the method signature.
My suggestion using your methods:
* GetXmlFilesOnAccount(accountid)
* GetSwfFilesOnAccount(accountid)
Retrieve account activitypointers by regardingobjectid(in your case accountid guid)
Loop through returned activitypointers
Get attachments for each activitypointer (activitypointer.activityid = activitymimeattachment.activityid)
Store attachments (disk, etc)
You don't even need two methods. You can retrieve all attachment file types for a given note (annotation) with a single method.
Hope this helps.
I recently started an Open Source Project on CodePlex to accomplish exactly that. Feel free to check out the Project's Web Page at:
http://crmattachdownload.codeplex.com/
You can also view the source code under the "Source Code" tab of that same page.
Pete

Resources