What is the variable name that is being displayed in the web-portal as the report name?
Example: if my RDL file is named Reportforseeingthings.rdl
I want the name displayed in the web portal as "Report for seeing things"
Is there a report properties variable that can be modified before deployment to handle this along with a server config to grab that variable instead of the file name?
Open to other solutions as well.
As far as I know there is no way to do this. You can set the file name and description properties but the report name will always be the file name. You can modify it once deployed.
So options are potentially:
Just rename the file in the solution
Manually edit after deployment
Create linked reports with the desired name, redeploying will update the base report but the linked report name will stay the same.
Put the required title in the description and have a script that updates the names on demand or as part of a trigger or scheduled job.
something like
UPDATE r
SET Name = Description
FROM ReportServer.dbo.Catalog r
WHERE Name != Description and Description IS NOT NULL
Note that even doing this, the breadcrumb trail in the web portal will still show the original name, but the list/card views will show the name you want.
Related
After I installed the JAMS product for v2019R1, I notice the field SOOrder.customerOrderNbr has a different label. I assume this happens, due to a graph or cache extension. The client wishes to change the label. Since I do not have the JAMS source code, what is the best way?
I have JAMS installed, but it doesn't change my field name, however, my approach would be to:
Add a new customization project
Put a 2 in the "Level" column
Add Screen SO301000
Locate and change the Display Name to your desired text
Publish your project
The key here is using the 2 in the "Level" column to resolve a conflict. See Acumatica Wiki reference for details
I had set the product name here:
And it's clearly listed in the direct editor,
But now after a successful build any reference to ProductName refers to the old product name I had, before changing it.
It's like InstallShield is ignoring my product name change.
How can this be fixed, or do I need to recreate the entire project?
The product name in the release media was overwriting the one set in the project.
i am trying to attach a document in list with the same name as previous document. in list, we don't have "Overwrite existing files" option. That s why i am getting error. Kindly tell me how can i overwrite previous document.
Error Description below.
The specified name is already in use.
The document or folder name was not changed. To change the name to a different value, close this dialog and edit the properties of the document or folder.0x81020067
i am unable to post a clear screen shot because i have 8 reputation only.
i am attaching in same list item only.
Out of the box attaching files with same name is not supported.
It is important that you deleted the file attached earlier since you want to attach the file with same name.
Otherwise you need to have custom solution to overwrite the file.
I'm having an issue setting the display name for a workflow on feature activation.
What I have got is a workflow that I create with a desired internal name (using SPWorkflowAssociation.CreateListContentTypeAssociation to get an SPWorkflowAssociation object). Once the name is set with that method call, I set the SPWorkflowAssociation.Name to the desired display name after that, add the workflow association to the list, and then call update on the associated list.
The result I see is that the internal name and the display name are both changed (internal name is required to link between the SharePoint list and the Client Side Object Model and we need this internal name as the display name is different for other languages).
Does anyone know how to set this properly in code? It looks like something that should be possible but I'm getting no joy from my investigations.
Thanks!
I got around this by using the description field to store a 'static' name and then later find associations via this description field rather than the internal name.
I'm having this problem and I didnt find any answers on the web.
I have a content type named "Document X" with the original "Document" as parent. (ID is 0x010100ACEA2663B318874AA9192CA9AF678614)
I already have a content type named "Document X 1" with "Document X" as parent. (ID is 0x010100ACEA2663B318874AA9192CA9AF67861401)
When I create a new content type named "Document X 2" with the parent "Document X", I get the error "A duplicate content type 'Document X 2' was found"...
I checked the ULS and the error isn't reported there. I can create new content type from any other content type (out of the box or others I created like "Calendar X") but I cant create new one from that "Document X". (And no I dont have any content type named like that.. whatever name I use, I get the same error)
Full error is:
A duplicate content type "Document X" was found.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: b9d36bb8-1a8e-4ef4-bbd0-fbdf8e70d73b
Date and Time: 1/24/2011 3:00:36 PM
This error is happening on my content type hub site but I use and create content type on this site only. I dont create them using Visual studio, its in a production environnement and we have to create them with the Site Settings or Designer but both give me the same error.
I know I dont have much info to give here, I just dont know where to look first..
If anyone have any idea that could help me, I would really appreciate it as I lost a few hours on this already and dont know where to look anymore...
Thanks a lot!
I found my problem, so if this can help some people some day.
Looks like SharePoint have some problems sometimes to update a field in the content database.
The field NextChildByte from the dbo.ContentTypes table is the problem.
Lets say I create a content type with ID 0x010100ACEA2663B318874AA9192CA9AF678614 with Document as parent (0x0101)
SharePoint will create an entry in the dbo.ContentTypes table.
When I create an other content type with the first one as parent.. The ID of this new content type will be 0x010100ACEA2663B318874AA9192CA9AF678614*01*) This 01 came from the NextChildByte field from the dbo.ContentTypes table.
Now SharePoint should update the dbo.ContentTypes table and set the field NextChildByte to 2 so the next content type created using the same parent will be 0x010100ACEA2663B318874AA9192CA9AF678614*02*
My problem was.. SharePoint didnt update the NextChildByte field so SharePoint was trying to create a content type with ID 0x010100ACEA2663B318874AA9192CA9AF678614*01* when it already existed...
In my case.. I finally have been able to delete the content type 0x010100ACEA2663B318874AA9192CA9AF678614*01*. When I recreated it, SharePoint did update the NextChildByte to 2 so I was able to create a more child content type after that.
EDIT: I found afterwards this blog post. Looks like this script could have fix it for me. This would be the best option since updating the database is not a solution.
http://www.mattjimison.com/blog/2011/06/21/a-duplicate-content-type-found-error/
Cheers!
After struggling with this issue for a good while (the fixes mentioned here didn't work for me), I have managed to find an alternative way to fix it.
In my case this error was happening when trying to use a Site Template (classic templates).
Before saving the site as a template, I opened the site using SharePoint Designer, navigated to All files -> _cts folder and deleted the content types from the site level. In my case there was already a content type with the same name in the Site collection level.