ID not updated in calculated column

I have a calculate column in a shrepoint list:
=ID&" "&Title
But I see that when an item is openend the calculation is not done and the ID and Title is only the Title...
Mike

for your requirement you can use an simple workflow
create a column for example staticID
when an item is created fill this with the ID
in the calculated column you can use
[staticID]&" "&[Title]
/blog
twttr @esjord

Similar Messages

Derived table 'tablename' is not updatable because a column of the derived table is derived or constant.

Hi Guys,
I have a With CTE table expression ,this cte gets the value from startdate and enddate
I need to insert this startdate and enddate into a table ,while inserting into table,i got the below error,
Derived table 'Datematrix' is not updatable because a column of the derived table is derived or constant.
below is the query i used,
declare @StartDate date='01/01/2013'
declare @EndDate date='12/31/2013'
;WITH Datematrix(AllocationDate)
As
SELECT @StartDate AS AllocationDate
UNION ALL
SELECT DATEADD(D,1,AllocationDate) AS AllocationDate
FROM Datematrix WHERE AllocationDate<@EndDate
Insert into Datematrix(AllocationDate)
select * from Datematrix
any guys update this solution.
Thanks
Bhupesh.R

;WITH Datematrix(AllocationDate)
As
SELECT @StartDate AS AllocationDate
UNION ALL
SELECT DATEADD(D,1,AllocationDate) AS AllocationDate
FROM Datematrix WHERE AllocationDate<@EndDate
Insert into Datematrix(AllocationDate)
select * from Datematrix
Hello,
Your CTE bases only on fix value = @StartDate , not on a table/view; here do you want to insert data to? This don't work in any way.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SPD workflow not updating a Lookup Column

I have a 2 lists (Computers & Lending Library) that both have a look-up column (Item Status) pointing to a 3rd list (Item Status - Category).
Both lists are properly looking up when manually edited via the web interface. When I try to use a SPD workflow to "Update or Create List Item" and I set the column in the Lending Library (Item Status) = Current Item (Items Status) the column is not populated.
I took the same value and updated a Text column and the value is "0".
The strange thing is when setting the (Item Status) it only gives me the options:
As Integer
Lookup ID (as Integer)
Lookup Value (as Integer)
What am I missing?
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

Its been a long time since I looked at this but yes we did figure it out.
Here is my Comment to myself on the lookup: "Must extract the [Item type] as a string and then lookup the corresponding List Item [ID] in the "Item Type - Category" list, use that value to update the "LendLib"[Item
Type]."
As suggested you need to reference the ID of the lookup, and I am caching that. Then when setting the [Item Type] column, by referencing the [ID] column in the Lookup list, then set your value to the Title of that lookup.
If I recall the issue was the lookup, if you don't use the [ID] then you don't actually retrieve the value from the [Title] column correctly.
My screenshots below are a bit confusing at first because my Lookup List is called "Item Type - Category" and the column in the 2nd list that is the
Lookup Column, is called "Item Type".
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

Sysdate is not updating to a column

I have a query that update column to sysdate. The problem sometimes it updates but sometimes not.
Here is my sample query.
Update table1 set a= 'a', b='b', c=SYSDATE where table1.no = '1'
Is there any issue of a SYSDATE.
Thanks a lot!

... and this is what language?
SQL> drop table tst purge
2 /
Table dropped.
SQL>
SQL> create table tst
2 (a varchar2(1)
3 ,b varchar2(1)
4 ,c date
5 );
Table created.
SQL>
SQL> insert into tst values ('A', 'B', sysdate);
1 row created.
SQL> select a
2       , b
3       , to_char (c, 'hh24:mi:ss')
4    from tst
5 ;
A B TO_CHAR(
A B 10:30:33
SQL> begin
2     dbms_lock.sleep (1);
3 end;
4 /
PL/SQL procedure successfully completed.
SQL>
SQL> update tst
2     set a = 'a'
3       , b = 'b'
4       , c = sysdate
5 ;
1 row updated.
SQL> select a
2       , b
3       , to_char (c, 'hh24:mi:ss')
4    from tst
5 ;
A B TO_CHAR(
a b 10:30:34
SQL> Are you executing the same statement within the same second (granularity of DATE) multiple times?

AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE was not updated

Hi,
I would like to raise one question on AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE of EBS 11.5.10 which is related to OBI Application 7.9.6.1
One customer mentioned that AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE was not updated whenever AP_INVOICE_DISTRIBUTIONS_ALL.PREPAY_AMOUNT_REMAINING filed is updated.
In reverse, I asked customer if it is expected in EBS 11.5.10 because I understand that LAST_UPDATE_DATE field is mandatory updated whenever any column is changed.
"1/ Basically, AP_INVOICE_DISTRIBUTIONS_ALL.LAST_UPDATE_DATE field is mandatory updated whenever any column is changed. If not, it must be a Source Application problem. Why do your Source Application person think that it is expected?
Ans: Because Source Application person think that Oracle apps basic application functionality for AP Invoice."
Could you let me know if it is really expected in EBS 11.5.10 or any other suggestions?
Regards,
ChongHak

If the last_update_date is not updated when another column in the table is updated, it is most likely a bug in EBS.
You should search metalink for a patch or raise an SR to obtain one.
Hope this helps,
Sandeep Gandhi

Using ODBC how do you identify a calculated column in a table?

I've a calculated column in my table. Is there a way to identify that column through ODBC functions? I need to identify the calculated column and make it read only. The function should support both SQL and Access databases. Please let me know if
there is a way to find out this column type.

Hello,
You can refer to the following article which list some ODBC Scalar Functions which you can used in the T-SQL query statement.For example
SELECT {fn TRUNCATE( 100.123456, 4)};
-- Returns 100.123400
Reference:http://msdn.microsoft.com/en-us/library/bb630290.aspx
As per my understanding, there is no built in declarative support for read-only columns. You can try to create a UPDATE trigger to achieving this. Or you can create a view with derived column from the source table. And then users cannot
update this calculated column on the view.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Views, not updatable???

Have run the script demobld.sql in schema SCOTT/TIGER and created the following view
SQL> @C:\scripts\demobld.sql
Building demonstration tables. Please wait.
Demonstration table build is complete.
CREATE OR REPLACE VIEW empdept AS
SELECT emp.empno, emp.ename, emp.job, dept.deptno, dept.dname, dept.loc
FROM emp, dept
WHERE emp.deptno = dept.deptno;
select * from user_updatable_columns where table_name like 'EMPDEPT';
OWNER     TABLE_NAME COLUMN_NAME UPD INS DEL
SCOTT EMPDEPT EMPNO NO NO NO
SCOTT EMPDEPT ENAME NO NO NO
SCOTT EMPDEPT JOB NO NO NO
SCOTT EMPDEPT DEPTNO NO NO NO
SCOTT EMPDEPT DNAME NO NO NO
SCOTT EMPDEPT LOC NO NO NO
I don't understand why the view is not updatable for the columns from the base table EMP, they should be. Does anyone know what the problem could be
Cheers
Fergus

Are you sure that you have all the primary keys and foreign keys correctly defined on those two tables?
SQL> alter table dept drop constraint pk_Dept ;
Table altered.
SQL>
SQL> CREATE OR REPLACE VIEW empdept AS
2 SELECT emp.empno, emp.ename, emp.job, dept.deptno, dept.dname, dept.loc
3 FROM emp, dept
4 WHERE emp.deptno = dept.deptno;
View created.
SQL>
SQL> select * from user_updatable_columns where table_name like 'EMPDEPT';
OWNER                          TABLE_NAME                     COLUMN_NAME                    UPD INS DEL
SCOTT                          EMPDEPT                        EMPNO                          NO NO NO
SCOTT                          EMPDEPT                        ENAME                          NO NO NO
SCOTT                          EMPDEPT                        JOB                            NO NO NO
SCOTT                          EMPDEPT                        DEPTNO                         NO NO NO
SCOTT                          EMPDEPT                        DNAME                          NO NO NO
SCOTT                          EMPDEPT                        LOC                            NO NO NO
6 rows selected.
SQL>

RELATED in Calculated Column or Calcualted Field?

Dear Team,
1] If I use the REALTED function to lookup a price in a Calculated Column like:
RetailPrice =RELATED(dProducts[RetailPrice])
and there are only 30 different prices (unique values) in a total of 39,000 rows, here are my questions:
Because the column has only 30 unique values, does this mean that it does not take up much RAM memory storage space?
Do the values get stored in the columnar data base in RAM memory the same as if the values were not from a Calculated Column, i.e. they were hard coded values?
Once I use this RELATED to lookup price, would it be more efficient to create a second Calculated Column to calculate Revenue like:
Revenue =ROUND(fSales[Units]*fSales[RetailPrice]*(1-fSales[RevenueDiscount]),2)
which I would then use in a Total Revenue Calculated Field.
Or would it be more efficient to NOT have second Calculated Column (Revenue) but instead to create a Calculated Field like this:
TotalRevenue:=SUMX(fSales,ROUND(fSales[Units]*fSales[RetailPrice]*(1-fSales[RevenueDiscount]),2))
On a side note, I have to say that trying to learn PowerPivot is really hard. It is so much different than Excel…
Sincerely, Mike Girvin

Hey Mike,
first of all I cannot agree to your comment that PowerPivot is really hard :-)
But regarding your questions:
1. Space in RAM or on your hard drive depends mainly on the amount of distinct items in a column. You could have 10 billlion rows, if there are only 2 unique values you'll probably won't have any impact on performance or memory. Regarding your 30 unique
items: I think you won't have a problem with these.
2. Calculated columns are treated the same way as columns coming from other sources. They are calculated during processing of the table. Simple answer to your questions: Yes
3. SUMX is generally better than calculating a new column and then running a SUM over that one. I'm not really sure, but I think it's because one is processed in RAM and the other on your CPU (don't ask me which one is which).
I hope I could answer your questions.
Kind regards
Please mark helpful posts and answers! :)

How to Make Calculated Column Hidden

I've created a few calculated columns; when I try to make them hidden (not to show on the View form), the options are not clickable:
The calculated columns that were created before the site migrated from 2010 to 2013 are still clickable.
What I am missing?
Thanks,
-Oleg

Maybe this might help
http://social.msdn.microsoft.com/Forums/office/en-US/4c07a7fc-d80b-4b3a-b3df-bd3e869ac606/set-a-calculated-column-as-hidden-in-a-content-type?forum=sharepointgeneralprevious
Thanks, Ransher Singh Click "Vote As Helpful"! if you think that post is helpful in responding your question click "Mark As Answer, if you think that this is your answer for your question.

Calculations not updating in fillable PDF

I have a fillable PDF with columns of numbers requiring totals. The sum function works but if I then change one of the numbers in the column, the total does not update unless I also change another field (for example, a description field or some other field that seems to refresh the calculation). Is this a bug and is there any way to force a refresh to avoid having to manually prompt the form to update the sum?
Thanks!

OK. I see the option now, but it lists all of the calculations in the entire form. My problem is that once all of the form data is entered and then the user changes a value, the sum is not updated automatically. Hope I'm explaining this properly..

The workflow could not update the item, possibly because one or more columns for the item require a different type of information. Outcome: Unknown Error

Received this error (The workflow could not update the item, possibly because one or more columns for the item require a different type of information.) recently on a workflow that was
working fine and no changes were made to the workflow.
I have tried a few suggestions, i.e. adding a pause before any ‘Update’ action (which didn’t help because the workflow past this action without incident); checked the data type being written
to the fields (the correct data types are being written); and we even checked the list schema to ensure the list names and the internal names are aligned (they
are), but we still cannot figure out why the workflow is still throwing this error.
We located the area within the workflow step where it is failing and we inserted a logging action to determine if the workflow would execute the logging action but it did not, but wrote the same error message.
The workflow is a Reusable Approval workflow designed in SharePoint Designer 2010 and attached to a content type.
The form associated with the list was modified in InfoPath 2010.
Approvers would provide their approval in the InfoPath form which is then read by the workflow.
Side note - items created after the workflow throws this Unknown Error some seem to be working fine.
We have deleted the item in question and re-added it with no effect.
Based on what we were able to determine there don’t seem to be any consistency with how this issue is behaving.
Any suggestions on how to further investigate this issue in order to find the root cause would be greatly appreciated?
Cheers

Hi,
I understand that the reusable workflow doesn’t work properly now. Have you tried to remove the Update list item action to see whether the workflow can run without issue?
If the workflow runs perfectly when the Update list item action is removed, then you need to check whether there are errors in the update action. Check whether the values have been changed.
Thanks,
Entan Ming
Entan Ming
TechNet Community Support

The workflow could not update the item, possibly because one or more columns for the item require a different type of information using Update Item action

I got error "The workflow could not update the item, possibly because one or more columns for the item require a different type of information "I found out the cause is Update Item action
I need to update item in another List call Customer Report ,the field call "Issues" with data type "Choice" to yes
then the error arise . please help..

Thanks for the quick response Nikhil.
Our SPF 2010 server is relatively small to many setups I am sure. The list with the issue only has 4456 items and there are a few associated lists, eg lookups, Tasks, etc see below for count.
Site Lists
Engagements = 4456 (Errors on this list, primary list for activity)
Tasks = 7711 (All workflow tasks from all site lists)
Clients = 4396 (Lookup from Engagements, Tslips, etc)
Workflow History = 584930 (I periodically run a cleanup on this and try to keep it under 400k)
Tslips = 3522 (Engagements list can create items here, but overall not much interaction between lists)
A few other lists that are used by workflows to lookup associations that are fairly static and under 50 items, eg "Parters Admin" used to lookup a partners executive admin to assign a task.
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

Calculated column - non-rolling rowsum where columns are not null

I have a calculated "Year total" column that sums 12 month columns. In our business $0.00 is not the same as null, so i have some columns without numeric data. My calculated column is only working when there is numeric data in all 12 months and i need it to work for rows where some columns are null.
Is there an easy way around this?

Figured out how to do this using the IFNULL function.

Can you have a calculated column in a table not a view?

We have a table which contains a series of rows
Key   Effective Date   Value
1       10/Feb/2006     123
1       23/Oct/2006      456
...We have a requirement to store an indicator that tells us which row is the most current and what the end date of the preceding row was so that we get something along the lines of:
Key   Effective Date   Value   Status         End Date
1       10/Feb/2006     123      HISTORY    22/Oct/2006
1       23/Oct/2006      456     CURRENT   NULL
...I can produce this result quite easily using the analytic function LEAD. My question is, is the answer to this problem to create a view over the table that includes the analytic function or is it possible to define a calculated column in a table that would populate/maintain this vale as part of a table definition?
And as I finish writing this I feel I've answered my own question but hey, there's no harm in asking how others have handled this kind of situation.
Cheers
Richard

My bias would be to create a view that did the calculation.
In theory, you could add those additional columns to a table and maintain the data via a set of triggers, but that would be substantially more complicated than the alternatives for little or no benefit.
A third option would be a materialized view. That might be easier to deal with if you want to have different indexing strategies for current and historical records or if the historical data is queried often enough and updated infrequently enough that it ends up being cheaper to do the calculation once during the update rather than every time the query is run.
A fourth option would be to use stored procedures to maintain the data and have that stored procedure expire the current row and add the new row.
Finally, you might consider version-enabling your table using Workspace Manager rather than writing your own code since Oracle has already written all this code for you.
Justin

ID not updated in calculated column

Similar Messages

Maybe you are looking for