It seems that one of the advantages to being able to export a snapshot in XML format is the ability to compare and merge changes between environments.
However, when I try to do this, zip the XML files again, and Import them, I get an error "Invalid snapshot format"
Is there a method to do what I'm trying to do?
Thank you all for the advice! The problem was indeed that I was zipping the extracted folder rather than just the contents. Doh!
Related
I am having a lot of excel files in the data lake. I am trying to read in dataflow and getting below error
"Read excel files with different schema is not supported now."
All my excel files are in the same format having the same column names. However, it's still coming above error.
Nor sure what is the issue? Can anyone advise how to solve this?
I see this is a known issue and is documented in the official MS docs. Can please try their recommendations.
You most likely intend to pull from multiple sheets in a folder. All the sheets do not have the same schema and that's the issue I had.
You'd need to identify the file with a different schema or take out the file path where it says wildcard path
Remove content from the wildcard path
Is it possible to get an item from it copy link from CSOM?
So get item from this format for both folders and files.
https://xx.sharepoint.com/:x:/r/sites/xxx/Shared%20Documents/%E2%80%99Sites-xx-xx-xx-xx.xlsx?d=w4f17cf6bd7094e988aecdf179acb3530&csf=1&web=1&e=0gneH9
I’m afraid not. As far as I know, there is no way to parse the share link like this:' https://xxxxxxx.sharepoint.com/:u:/s/dev/EUDdsBKYArRDobXz-drQ4_wBh07dg8x_-XtB2Vm4A9B7Mg',so we could not know the information about the file.
I have written a bit of automated code that checks a SharePoint site and looks for a ZIP file (lets call it doc.zip). If doc.zip is found, it downloads it, and then checks for a file (say target.docx). doc.zip is about 300MB, and so I want to only download where necessary.
What I would like to know is that given SharePoint has some ZIP search capability, is it possible to write code using CSOM (c#) to find doc.zip, and then run some code to retrieve the contents of doc.zip without downloading it.
Just to re-iterate, I am comfortable with searching for files in a folder on SP, downloading the file, and unpacking zip entries. What I need is to retrieve a ZIP files content on SP without downloading it.
E.g. is there a SP command:
cxt.Load(SomeZipFileQuery);
cxt.ExecuteQuery();
Thanks in advance.
This capability is not available. I do like the idea. Having the ability to "parse" zip files on the server side and then download the relevant bits would be ideal. Perhaps raise this on uservoice to see if others also find this us https://sharepoint.uservoice.com
Ok, I have proven yet again that stubbornness will prevail.
I have figured out that if I use the /_api/search?query='myfile.zip' web REST API to search for my file, this search will also match ZIP files that contain the file I need. And it works perfectly.
Of course there is added (pain) of parsing an XML response, but it works very nicely for my code example.
At least if someone is looking for this solution here it is. I wont bore anyone with code, as the /_api/search has probably been done to death already on other threads.
I have a notebook full of content I am looking to publish online, but the problem I am running into is I can't find a method that will retain the original formatting. I understand I might have to recreate the navigational tabs/pages, but I trying to avoid having to recreate the content in a different format.
Is there anyway to export a form of the content that maintains the tables, text formatting and etc.?
Why not get a read only sharing link to your notebook?
I think the closest thing to what you want is this:
https://thenextweb.com/apps/2015/05/22/microsofts-new-wordpress-plugin-lets-you-directly-publish-your-onenote-documents/#.tnw_o7KuyR9D
I'm receiving a "Failed to extract the cab file in the solution" error when I try to deploy my wsp using stsadm -o addsolution -filename...
I've open the wsp as a cab and checked that there are no duplicate files in there as I understand that can sometimes cause this issue.
The issue only started when I tried to include a custom field type as part of my solution, to do this I added the following to the ddf
..\CustomFields\ShortMonth\ShortMonthControl.ascx ..\CONTROLTEMPLATES\ShortMonthControl.ascx
..\CustomFields\ShortMonth\fldtypes_shortmonth.xml ..\XML\fldtypes_shortmonth.xml
and
<TemplateFiles>
<TemplateFile Location="CONTROLTEMPLATES\ShortMonthControl.ascx"/>
<TemplateFile Location="XML\fldtypes_shortmonth.xml"/>
</TemplateFiles>
to the manifest.
I've tried taking it back to just references to the ascx in both but it doesn't see to help.
Any ideas?
Check that you don't have any special characters in your files. They might have sneaked in as a result of copy-paste. For example, the way your code sample renders on this page, it has the (`), which shouldn't be there.
Do you need the "..\" in your DDF?
The issue is more likely due to invalid names for files you are deploying on SharePoint 14 hive folder. If you are using parenthesis ‘(‘, ‘)’ in file names or special characters like # in file names, this issue will occur.
Remove it and issue should vanish.
I just know I have had the same issues and I think I made a note of it at work somewhere (I´ll check that tomorrow and post back here if I find something). I just can´t remember how I fixed it right now (maybe it was a slash the wrong way / vs. \..hmm).
I did a search for it on google (which I think you have also done). Found this (check it out):
http://www.codeplex.com/wspbuilder/WorkItem/View.aspx?WorkItemId=7385
The List Instance Name I had was "MyListInstance (List Instance)". I removed the brackets from the name and it deployed without issues.
Check the .ddf file for a line that could have been accidentally duplicated. Apparently sharepoint doesn't like that!
A reboot solved my 'Failed to extract cab file' problem. There were some updates installed and an reboot was required. Was not clear that this was related but it helped.
Something would have gone wrong during the build of WSP.
Re build the WSP and Deploy- it should work fine.