The file you've attempted to upload is larger than the maximum allowed by the system. We typically recommend that you do not upload files larger than 1 GB. In some situations, an exception can be made for documents larger than 1 GB.
I think what you are asking is whether the path to the document library created by CDS exists in the Document Location entities. It doesn't but the path exists in the Document Location entity so its easy to associate the document stored in the document library with the entity. I would suggest that you create the folder when you create the document and then create the document location entity with the document library. This is easier for the user to set the path to the document library.
If you decide to create the document location entity with the path to the folder then you will have a couple of options:
Add the document to the document location entity.
Add the document to the document location entity, and then create a new document location entity with the document and the new entity. (If you do this you can use the same GUID for each document, and you can easily delete the document in the first document location entity, without deleting the document in the CDS entity.
If you add the document to the document location entity, if you browse the Document Location entity for that record it will have a path to the document added. I think the easiest thing to do is to add the document to the document location entity and then when you want to associate a document with an entity you create a new document location entity with the document and the CDS entity and save the entity.
In addition to the libraries loaded for the RAML file itself, if the RAML file references other RAML files, those files are also loaded and so it is also possible to add libraries to the set of libraries loaded for a MEX file, by adding a reference to the MEX file in the RAML file. To do this, use the `use` nodes under the `extends` node that describes the MEX file in the RAML file. 827ec27edc