I'm experimenting an issue when I export customizations made by Studio tool, any custom fields are not exporting. I mean, when I load the package created in developer server to the production server, there are not custom fields in EditView, there are "native" fields only.
I'm using SugarCRM 6.1.6 (I know, it is an old version, but I can't update it right now)
Regards
Mauricio M.
You may just need to do a repair and rebuild - that's the likely quick fix. Alternatively, ensure that the package on the dev server exported both the custom fields and the custom layout metadata (i.e. the edit and detail view layouts). If it did, double check the permissions in custom/modules//metadata to ensure that the files were able to be uploaded and are readable by the web server.
Related
As we have below command to extract all the projects/reports from obiee12c analytics
exportServiceInstance( '/oraclehome/user_projects/domains/bi','mycompany.facility', '/workDir', '/scratch/exportDir')
This command provided extracts all metadata information of every projects and folders and report present in analytics as a archived bar file.Is there any other way were I can get metadata information of particular report or project which I need and not all the projects as a bar file or any?
OBIEE comes with several client tool with the "Catalog Manager" being the admin tool of choice for handling catalog-related tasks like yours. It exists as a GU and a command line both so you can also automate/script repetitive tasks like reporting on your reporting objects.
Have a look at the official documentation as it's too much text to just post into an answer here and you may come across things you want or need in there which go beyond your initial question here:
https://docs.oracle.com/middleware/12211/biee/BIESG/GUID-E804B1AF-B792-4929-BE47-33CA0F668715.htm#BIESG340
I you only need the reports you can export your reports folder directly from the catalog in OBI web interface or using "Catalog Manager" as suggested by #Chris.
For the repository you can connect Online to your server then from file -> Copy As
Note : exporting the service instance is used for environment migration, it's easier to move all what you need with one bar file (for example having DEV PROD environments).
I am trying to move document libraries, from one site collection to another and retain of the metadata such as Modified By, Date Modified etc.
I have tried using the 'move' function within SharePoint 2013 Content and Structure but unfortunately this doesn't extend to across site collections.
I have tried multiple PowerShell scripts they successfully copy the file from one Site Collection to another but do not retain the metadata.
Any ideas, would be greatly appreciated.
Thanks.
have you tried saving the library as a template? You can mark the template to keep the contents.
Then you can deploy a new library from that template (Site actions / More options / Template name), and after that delete the template.
Additionally you can move it between servers. Go to the Site settings, there to the template gallery and download the template you just created. Now you can move it to another server or application.
Hope it helps.
Take a look at the SharePoint migration tools. Some of them offer free trials for limited amounts of data.
i just modify an file from kentico CMSApp project.
The path:
CMS\CMSModules\Content\CMSDesk\Properties\Menu.aspx
i change an input from cms:CMSTextBox to cms:MediaSelector.
In kentico dashboard -> pages -> Properties -> Navigation
After that i deploy the CMSApp_MVC project, and copied the files from the folder i mentioned.
Now it doesnt work on production environment.
Help please.
It is highly recommended not to modify Kentico system files unless you have no other options. Your current change is not supported and instead of doing that I would recommend to create a Custom page type field using whatever Form control you like to hold your value - just don't change the file you mentioned directly.
You can then work with that field just like you would with any other Document/TreeNode field.
PS: Kentico 9.2 does not exist.
I cloned some magnolia content app examples and can't understand, how to generate magnolia bootstrap xml files. They are too big and to write them manually is too hard.
I think there is a way to generate them automatically.
Magnolia Bootstrap Files are created within Magnolia. Just create the content you want to bootstrap and export it. Some Apps like the pages app or the config app have an "export" action in the action bar. It is also possible to use the export app to create bootstrap files for all kinds of magnolia workspaces.
As Thomas said, you should not hand write bootstrap files, but instead export configuration or data you want to bootstrap from Magnolia.
Since "what you want" seems to be creation of apps, you might want to look at a script to create them (so you can them export such created app as a bootstrap file) mentioned here.
HTH,
Jan
I am a new user of orbeon and am trying to some exercise with orbeon's code. I have downloaded orbeon source code from git. I have made a war file (with ant orbeon-dist-war) and placed it in tomcat. Everything is working fine. Then I follow the tutorial and make "my-bookcast" application mentioned there.I found the application source code at "/WEB-INF/resources/apps/my-bookcast" and I know which database is used and where the data are saved. But my questions are
When I create form using orbeon form builder using the video tutorial mentioned in www.orbeon.com, using mouse and keyboard only where the form saved? How can I see the source code (like "my-bookcast") of the saved form?
Can I use the form along with source code in other application, independent off orbeon?
Update: Can anyone tell me, if I want to see the data stored in exist-db then how can I do this. I heard about oxygen, which can be used as a exist-db browser. In that case where can I found the exist-db related configuration in orbeon to connect with the built-in exist-db?
Out of the box, the form definitions and form data are stored into the embedded eXist database. The source code you can see directly from Form Builder, with "Edit Source".
No.
Regarding the question in your update: you can disable the orbeon-exist-filter eXist security filter in web.xml, then should be able to connect with oXygen either via exist-xmlrpc-servlet or exist-rest-servlet which is mounted on /exist/rest/*.
Graphical view
You can find this icon on Right Top.
After clicking, you will get this popup and that's the source