Strange issue- In a Concat() formula within Acumatica Report Designer, I have a string series. It's only showing incomplete data from the field though.
Example, the Concat() formula is this:
Concat([ARInvoice.CustomerLocationID], '-M-' , [ARInvoice.RefNbr] )
(So, trying to concatenate the Location with '-M-', followed by the full Invoice Reference number.)
I'm expecting to see this value: FACILITY02-M-AR006530
Instead, Report Designer returns this value: FACILITY02-M-AR
I confirmed this isn't a field-size issue or a text alignment issue. It seems like Acumatica is just not returning the full value for Invoice Reference number.
Ideas?
I see the same strange behavior, but I found a solution.
In your expression, wrap the expression with CStr
CStr(Concat([ARInvoice.CustomerLocationID], '-M-' , [ARInvoice.RefNbr]))
Related
I have a custom page type for Staff and there's a field called Function. I have a WHERE condition in a repeater like this: Function LIKE '%insurance%' and got an error Incorrect syntax near the keyword 'Function'
From the error I guess Function is a reserved keyword, so I changed the field name to BusinessFunction. However right after changing the field name, I noticed all the values for that field become blank. If I changed it back, the values are back to normal. The question: is there a way to change the field name while keeping the values that are already there -- without access to the backend database?
Wrap the word Function in brackets like so should resolve the problem: [Function]
When you say the values of the field are blank do you mean on the display side in the repeater? Have you changed the transformation to use the new field name? Have you updated the Columns property of the repeater to use the new field name vs. the old one? It will not lose all the data, you just need to ensure all the values of the property/field name are updated everywhere including any custom code you might be using for this page type.
In my list i have created calculated field to get the difference between the last modified date and today's date.
I use the formula
=datedif([modified],[today],"d")
It is throwing an error : The formula contains reference(s) to field(s).
Please advise.
I do not have a separate column to hold today's date.
Regretfully, you cannot use [Today] for calculated fields. Calculated fields only update when an item is modified, so the Today Trick of creating a column named Today, setting your calculated field, then deleting that column, is a bad move.
You have a couple options, the best of which is probably to use JavaScript within a Content Editor Web Part on the page to do the calculation for you. You could also try using SharePoint designer and custom XPath and xslt to get "days since modified" to appear on your page.
Generally, if you want something to identify items that haven't been modified in a while, it should be done with filter library views: they can use [Today], and they don't require tricks or workarounds.
I am getting this error inconsistently while working with Excel table connected to a SharePoint list. Similar issue has been reported on TechNet and it indicates it could be due to certain column types such as Date and Time, Lookup, or Calculated ... I would like to know when and why exactly this happens? What's more interesting is the error is not consistent, it just happens randomly.
Thanks in advance.
MOSS 2007 on Windows Server 2003 x86 Standard Edition
In my case I exported the list into Access and made some changes which I synched with Sharepoint afterwords.
I found the solution under List Settings > Change Column:
As I exported the List in excel, I saw the error message "Cannot get the list schema column property from SharePoint list". However excel was able to read the data from Sharepoint but two columns were missing.
The problem was that the columns with a date format (Not date and time, only date), had "Today's Date" as default value initially. After the synch, the default value was changed into the manual input option below "Today's Date". After I changed the default value back to "Today's Date" the problem was gone. So it was a problem about incoherent cell value and default value. This could also happen in different cell types.
I was debugging this same issue just recently. I ran into a lot of explanations that an update had changed the default value for the Date columns. Solutions presented were to set a new, real default value, save, then clear it out again. Others suggested converting to Text and converting back.
In my case I was able to identify the column was not a Date field but a Lookup field. I was pulling my hair until I ran across this blog post. It mentioned this problem could happen with Lookup columns which pull data from Calculated columns. That's exactly what my problem was. Except it worked when it was first created. It wasn't until after a user accidentally deleted the Lookup column and we recreated it. That's when the trouble started.
Interestingly we have another Lookup column bound to the same list to a different calculated column but it does not trigger the error.
I did a more thorough write-up and explanation on my own blog detailing the steps we went through until we solved it.
In my case, the solution was to check the data pulled by a lookup column. After i selected the value in the lookup column, i pulled also other column data related to that value. The secondary column of the lookup contained some weird characters "#&" . After removing it, the export worked.
With office 2013 there was no problem even with the special characters.
I have a calculated column in a custom SharePoint 2007 list, with the following formula:
=CONCATENATE("IR-",[ID],"-",LEFT(UPPER([Title]),25))
If an item is created in the list, everything is fine, however, when an item is updated the [ID] column is no longer in the calculated column for that item.
So, on creation: "IR-40-TheTitleIsHere", but after edit, it is, "IR--TheTitleIsHere".
Anyone have some insight on why this would be happening?
I confirm the behavior mentioned above. Any Add/Edit will wipe out the [ID] portion. If you edit the column in the list and update the formula, it will update ALL list items to be correct (until you do an edit on the item).
I found this post that mentions the same problem.
Sounds like the only solution would be to make a simple workflow using SharePoint Designer that would update a text field in your list.
I had an issue similar a while back. Through other blogs and experts, I discovered that the [ID] column should not be used in a calculated column because it wreaks havoc and causes many errors. Sorry - remove the ID column and you should be fine.
This question is a little old, but I had the same issue and found a solution for it. It is a pretty specific fix and won't help everyone -- it involves using javascript in a content editor web part to update the calculated field.
This site -- http://blog.pathtosharepoint.com/2008/09/01/using-calculated-columns-to-write-html/ -- gives an example of how to use javascript in the same manner that I used it.. the important block of code is the first while loop. The point is to grab the out of box ID column from the list and update whatever calculated field needs the ID.
In my case I had a URL in a calculated field that required the ID as a parameter.. of course that wouldn't work normally because you can't put the ID in a calculated field. What I did was I put "?ID=null" in the ID parameter of my calculated field's url, I then replaced that with the ID that was retrieved using javascript.. so whenever the page is loaded, the js kicks off and updates all of the URLs to have the correct ID.
I know this is very old but I couldn't find a newer version of the question anywhere else and the answer above from ferr solved the problem for me but isn't very clear so I thought I'd update it.
This assumes that you want to use the ID in the output HTML (for example within a link), I think this is fairly common.
Using the javascript from the pathtosharepoint link I added in the following to get the id with an if statement for safety:
if (HTMLregexp.test(CellContent)) { //original pathtosharepoint line
if (NodeSet[i].parentNode.getAttribute("iid")){
var SPID = NodeSet[i].parentNode.getAttribute("iid").split(",")[1];
CellContent = CellContent.replace("SPIDReplace", SPID)
}
NodeSet[i].innerHTML = CellContent; //original pathtosharepoint line
This is put in the while loop of the latest pathtosharepoint fix at time of writing. This works for me on SharePoint 2010.
Note: Include the string "SPIDReplace" in your calculated column to get it replaced by the item ID.
pathtosharepoint page: http://blog.pathtosharepoint.com/category/calculated-columns/
pathtosharepoint code: http://pathtosharepoint.com/Downloads
I have a custom content type with custom fields. I'm trying to create a custom document information panel using infopath. Whenever I try to do that infopath gives me this error
propertySchema0.xsd#/schema/element[1][#name = 'properties']/complexType[1]/sequence[1]/element[1][#name = 'documentManagement']/complexType[1]/all[1]/element[1]
Reference to undeclared namespace prefix: 'ns1'.
Any one have seen this before?
There's nothing unusual about the fields in the content type, other than that their names are in unicode characters, could that be the problem?
Update:
Ok, so the unicode characters in the display names have nothing to do with the error. The columns I'm using are pretty standard columns, mainly text, integer and boolean type columns.
Anyone have any idea what might be causing this?
Ok, so the unicode characters in the display names has nothing to do with the error. The columns I'm using are pretty standard columns, mainly text, integer and boolean type columns.
Anyone has any idea what might be causing this?
I've finally figured this one out. The SourceID needs to be set inn the field type definition in the feature manifest. Setting SourceID to the same value as the builtin fields dows the trick. Like this SourceID="http://schemas.microsoft.com/Sharpeoint/v3"