I'm working on a SAPUI5 Master Detail application with Odata model Two Way Binding.
When I click on a header element and enter data for its items and click submit, the entered data is still there.
Even if I click on another Header element, if I go back to the previous header element its data is still there.
I want the entire model to be completely refreshed on every click on a header element.
I tried SubmitChanges method, but it's not working ...
Check out the below sap archive
https://archive.sap.com/discussions/thread/3649362
Related
I have a ajax download functionality in my MVC webapp.
User can select a criteria and click on export button. Internally it will fetch data and return an Excel file. up to this functionality is working fine.
But the issue occurs, While one download process is running and now user changes the filter criteria and again click on export button. Now two download processes are running. Whichever process completes first will return file to download. Now the user can see Open, save, cancel option to download first file. As this stage when second download request is also completed and returns file to download. When I opens one file the another file download option is also lost.
Initially I thought it might because both the files are having same name. So I made changes to set unique file name for every request. But It still gives only single file to download.
Can anyone help me on this?
edited :
On other pages where I have two different types of files to download, the above functionality works successfully.
In none ajax requests, page can only be waiting for one response.
In order to solve that problem and wait for multiple responses you should use target attribute with value "new" as the following code depicts:
Your download Text
The above code makes each response to be downloaded in a new tab.
I am using CoreData for my Project.
In first image i selected Site to create the entity object.
After clicking the next. If you see the second image, Game files are created.
Here i want to create entity object for Site, But it is creating Game entity object. Please help me out.
Make sure the class name in the right hand panel is what you want it to be. You can also access this in the configuration editor for the Default configuration.
Right side panel
Configuration
I have created a module in Orchard cms, in which I created a form to collect the data and also added a image field(media). Now I have created a separate view(.chtml) to display the list of data that are collected from form in module in admin section.
Now suppose I added few data, let it be two entry in the form and I display all the two entry in newly created separate view. But When I delete the one of entry in form in admin section, it deleted and disappear there, but it is still present in database and visible in my newly created separate view. Can anyone please help me to know, how to detect the delete entry in Orchard Cms Database. I think it is soft deleted, because it is still in database but not showing in admin view section (dashboard).
Yes, Orchard always does soft deletes on content items. There are two boolean flags - Published and Latest - kept in table Orchard_Framework_ContentItemVersionRecord for each version. If both are false, the version is considered deleted. If there is no published and latest version for a given item, the whole item is considered deleted.
If a deleted item still appears in your custom view, you're probably doing some custom query in your code and you may need to revisit it. ContentManager fetches published versions by default (Get and Query methods) only.
We use extensively (from an application) in the Document List API the fact than a file / document can be assigned to more than one collection, in order to work in a similar way that labels. Has this been deprecated? At least from the web user interface, only one folder can be assigned to one file.
Working fine here and multiple collections can be successfully assigned.
Right click a file, Choose "Organise" and check the box next to each collection you want the document to be a part of.
I have an infopath form template at
https://mysite/Shared%20Documents/MyForm.xsn
If you click on the xsn file in your browser and hit "open" it opens up the template and allows you to fill it in and then hit a submit button which saves an xml file to
https://mysite/administrator/In%20Process/filledOutForm.xml
Then if an admin comes into sharepoint and clicks the filled out infopath form, it opens up fine.
However if the user first saves https://mysite/Shared%20Documents/MyForm.xsn locally, then the link to the form template appears to be stripped (i think because the actual form template is actually local now, rather then being viewed from the sharepoint). thats fine and dandy, they can still submit the form, and it gets saved to https://mysite/administrator/In%20Process/filledOutForm.xml but now its missing the href link to the form template. now when an admin tries to open the filled out form, they get an error saying infopath cant find the form template.
I can follow the instructions listed here:
http://blogs.msdn.com/b/infopath/archive/2006/11/01/relinking-forms-and-form-templates.aspx
to "relink" the form to the form template, and that fixes the issue, but I want to fix the underlying issue. How do i make it so that users either cant save it locally (breaking the href to the form template) or make it so that the link to the form template stays there, even if they save the form locally?
Sadly it is more due to training and configuration. We end up "fixing" this all the time (funny it is the same users that seem to have the problem). Some helpful ideas.
Remind your users that the XSN is a template and the XML is their data. They should never really need to save the template. A good analogy is Word dotx and docx - you open the dotx (template) but when you save it defaults to docx (data) - InfoPath does the same thing.
Usually when you "open" an XSN it opens in data mode. When a user clicks save the default is to save as XML. They have to "design" or "open in design mode" (or switch to design mode once open) to actually modify the XSN itself. Remind the users that when they go to save - if it is trying to save as XSN something is wrong and to back up a step.
We also tried to protect the XSN either by security or location so that the common users don't have rights to write/overwrite it - they can only save XML. That way even if they do mess up the system will block the save. Of course that doesn't keep them from local copies.
Just be open minded about it - there will always be cases where you have to go back and relink the template. The more you can reduce the better but they still happen ("but I wanted to keep the template locally so I didn't have to keep going to the website").