If statement formula in Sharepoint 2013 returns and error

Hello
I am trying to create an IF statement and keep getting the following
Technical Details
Learn more about the syntax for formulas.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 6f86ad9c-2538-00bf-c686-c2b81c8e95eb
Date and Time: 8/11/2014 6:00:02 PM
I was told to create it in Excel then copy/paste into SP. Here is the formula and it works perfectly in Excel:
=IF(A11="H8K77AE - Face to face training ($750 USD/Day)","SAP",IF(A11="H8K78AE - Virtual Instructor Led training ($500 USD/Day)","SAP2",IF(A11="H8K79AE - Break/fix demos on lab equip WITH Instructor
($400 USD/Day)","SAP3",IF(A11="H8K80AE - Break/fix demos on lab equip WITHOUT Instructor ($200 USD/Day)","SAP4",IF(A11="H8K77A1 - Face to face training ($750 USD/Day)","Fusion",IF(A11="H8K78A1 - Virtual
Instructor Led training ($500 USD/Day)","Fusion2",IF(A11="H8K79A1 - Break/fix demos on lab equip WITH Instructor ($400 USD/Day)","Fusion3",IF(A11="H8K80A1 - Break/fix demos on lab equip WITHOUT Instructor ($200 USD/Day)","Fusion4",""))))))))
The only difference is I change the cell references of "A11", to the field name in SharePoint "[SKU#]". when I hit OK I get the error above. Does the field name not need to have the brackets around it or is it something
different?
I am really hoping someone can help here as this should be rather simple and not sure why I don't get a result based on what is selected in the [SKU #] field
Thank you for your assistance.
Amathyst

Try using the actual column name.

Similar Messages

Can we use SSRS in sharepoint 2013 standard and sql server standard edition

can we use SSRS in sharepoint 2013 standard and sql server standard edition
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Yes you can. You do lose some features:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Deploying SSRS Reports to SharePoint 2013 Result in Error

We are trying to deploy SSRS reports developed in VS 2012 to SharePoint 2013. Whenever any user deploys the report, they receive the following error.
Error 1
Report Server has encountered a SharePoint error. --->
Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. --->
Microsoft.SharePoint.SPException: The list item could not be added or updated because duplicate values were found in one or more fields in the list. --->
System.Runtime.InteropServices.COMException: The list item could not be added or updated because duplicate values were found in one or more fields in the list.
Has anyone received this error and know of a solution?
Thanks in advance for your assistance.

Hi jbud55,
According to your description, my understanding is that there is an error when you deployed SSRS via to SharePoint 2013.
This error displays that there is a column that does not allow duplicate value in the list. So, please check the list columns.
In addition, as this issue related to SSRS, you can also create a new thread on SQL Reporting Serivces forum, more experts will assist you with SSRS.
SSRS forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=sqlreportingservices
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

I recently just bought a Toshiba 3TB External Hard Drive. I am trying to partition it on my macbook, but it keeps returning and error message. The only thing I have changed is renamed easy drive.

I recently just bought a Toshiba 3TB External Hard Drive. I am trying to partition it on my macbook, but it keeps returning and error message. The only thing I have changed is renamed easy drive.

Your problem is not Boot Camp, in fact, is your optical drive. Win XP requires indeed sp2, but also the internal drive, does not work from external optical drive.
For other possible tricks, please use the appropriate Boot Camp forum, not here. Mac OS X may be installed from both external and internal optical drive and/or internal/external partition of a disk, any disk. Windows is not so generous.

Reporting Services in both SharePoint 2013 connected and native mode?

Is it possible to configure Reporting Services (SQL Server 2014) to support both SharePoint 2013 connected mode and local Report Server in native mode on the same server using multiple instances of RS? The reason for this setup is to avoid having to purchase
SharePoint Enterprise CALs for other users than analysts and still be able to publish standard reports to all employees.
Management and analysts -> Custom reports published through SharePoint 2013 Enterprise (SP2013 ECALs and SQL Server 2014 core license). Data alerts and Power View enabled if possible.
All employees -> Standard reports published through Native Mode Report Server (SQL Server 2014 core license). Possible subscriptions.
I find the official documentation a bit lacking in this area but can't find anything stating against the above. It would be greatly appreciated if someone could confirm before planning the installs.
What I'm aiming for is somewhat similar to the "2 Tier Topology" described at: Example
License Topologies and Costs for SQL Server 2014 Self-Service Business Intelligence
With the difference that there is a separate SQL Server 2014 server used both by SharePoint and as a standalone BI-server.
SharePoint EE + SQL Server 2014 EE
Excel Services
SSRS Add-in (Reporting Services, Power View)
SQL Server DB for SP Content, Configuration and Service Application DB:s
SQL Server 2014 EE - SharePoint + Standalone for BI
SSRS SharePoint Mode
SSRS Native Mode
SSAS (Not in SharePoint mode, skipping PowerPivot for now. Would Power View still work?)
SQL Server DB for Data Warehouse
= 1 x SharePoint EE Server Licence, 2 x SQL Server 2014 EE Server Licenses?
Deployment
Topologies for SQL Server BI Features in SharePoint - Actually gives a good overview in the section "PowerPivot for SharePoint
2013 and Reporting Services Three Server Deployment". Just remove PowerPivot Service from Server 1 and change the Analysis Services in Server 2 to a regular native multidimensional mode. Server 2 would also be used for native Reporting Services.
Fallback or even beneficial option to install SSRS in SharePoint mode on the SQL Server instance used for content and configuration?

Hi Daniel Wikar,
As per my understanding, you want to install two SQL Server instances on the same server, and configure one of the Reporting Services to SharePoint integrated mode, another to native mode.
According to my knowledge, multiple instances of Reporting Services on the same computer, where one instance runs in SharePoint integrated mode and the other instance runs in native mode is supported. But we must run all report server instances at the same
level. For example, if we are using SQL Server 2014, all report server instances must be SQL Server 2014.
Besides, Analysis Services and Reporting Services can be installed as standalone servers, in scale-out configurations, or as shared service applications in a SharePoint farm. Installing the services in a farm enables BI features that are only available in
SharePoint, including PowerPivot for SharePoint and Power View.
For more information about Feature Comparison of SharePoint and Native Mode and Supported and Unsupported Configurations, please refer to the following documents:
http://msdn.microsoft.com/en-us/library/ms157231.aspx
http://technet.microsoft.com/en-US/library/bb510781(v=SQL.105).aspx
For detailed information regarding to the license issue, please call
1-800-426-9400,
Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
You can also visit the following site for more information and support on licensing issues:
http://www.microsoft.com/licensing/mla/default.aspx
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.

SharePoint 2013 RTM and WIndows Server Core 2012

Hi,
I've got a simple question I couldn't find the answer on the net.
Is SharePoint 2013 officially supported (supported, not just working almost fine) by Microsoft if installed on a Windows 2012 Server Core? Does it depend on the roles of the farm?
If possible I would like to have official sources from Microsoft.
Thanks for helping :)
Cya

First, I guess I should start with a disclaimer. I do work for Microsoft, but I do not speak for the product group and have no authority over what is/is not/will/will be supported with regards to SharePoint 2013.
My assumption however is that we'll treat it the same way we did for SharePoint 2010. It should work just fine and should be supported. The software requirements that Jason points out indicate that SharePoint requires Windows Server
2012 Standard or DataCenter. Choosing to install in core or with a UI doesn't change the fact that you've installed either Standard or DataCenter.
Also, from a support perspective, you can use remote tools in order to perform common tasks, such as checking the event log, restarting services, etc.
Roger Cormier
Microsoft
Premier Field Engineer, SharePoint
Blog: http://blogs.msdn.com/b/rcormier/
Twitter:
LinkedIn:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SharePoint 2013 (Foundation) and Outlook Web Access WebPart (OWAPart)

Hi, I've read most MSDN forum threads relating to this topic, however, I haven't seen my issue anywhere.
We're running SP 2013 foundation, and I want to use the Outlook Web Access web part. I followed the steps outlined here:
http://blogs.msdn.com/b/shawa/archive/2014/06/01/owa-web-part-in-sharepoint-2013.aspx
(Sorry, can't add link since I'm new around here)
To make the WebPart available in the site collection. Which worked.
When I try to actually add the WebPart to a page though, I get an error message stating: "There was an error adding the component to the page" (roughly translated from french).
If I try to see the web part properties from the site settings > Web Parts, I get a SharePoint error page, and the help link yields no information.
Most problems I've seen are with the actual configuration of the WebPart, but I can't even get to that step.

I dont think you can use Outlook web app for foundation. This is not possible because those Web parts use Microsoft.SharePoint.Portal.dll
which is not avaliable and registered on SharePoint Foundation.
Instead of using the OWA web parts, you could also try using the Page Viewer web part and set it to the OWA URLs...
If this helped you resolve your issue, please mark it Answered

Windows 7 with SharePoint 2013 Foundation and Visual Studio 2013

Hi,
I am begginer with Sharepoint 2013 Foundation.
My company installed Sharepoint 2013 Foundation on a virtual Server. I installed
Visual Studio 2013 on my local computer. Also i created a developer site.
Based on http://msdn.microsoft.com/en-us/library/office/jj220047(v=office.15).aspx#RDOverview I installed Office
Developer Tools for Visual Studio 2013 on my local computer.
I am trying to remotely develop apps
with Visual Studio 2013. In the option What SharePoint site do you want to use for debugging your App? i put the url
of developer site.
First of all, i had to choose if the apps will be SharePoint-hosted or Provider-hosted apps. Based on http://msdn.microsoft.com/en-us/library/office/fp142379(v=office.15).aspx and http://msdn.microsoft.com/en-us/library/office/fp142381(v=office.15).aspx,
i decided to followed SharePoint-hosted because is the only type that applies to SharePoint 2013 Foundation.
I followed the steps of http://msdn.microsoft.com/en-us/library/office/fp142379(v=office.15).aspx, which is the quide for How to:Create a basic SharePoint-hosted app. In Step 10 for deploy my app i get the following error:
Error occurred in deployment step 'Install app for SharePoint': Failed to install app for SharePoint. Please see the output window for details.
What is the problem?
Also, the visual studio need to be installed on the server where sharepoint was installed?
Moreover, do I need app catalog for testing and deploy apps?
thanks, Aphrodite

Hi,
According to your post, my understanding is that you have an issue about creating app.
Per my knowledge, the issue is caused that you don’t configure the app catalog URLs from the central administration.
It means that we should create an App site catalog site collection to hold our Apps.
More reference:
http://www.sharepoint-journey.com/app-development-in-sharepoint.html
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Items greyed out after upgrading and migrating to Sharepoint 2013 - Open and Check Out + Manage Document Option

Hi there,
Following a migration to SharePoint 2013, the follow options have been disabled (Open and Check out + Manage) (see below). These are critically important functions and make it very hard to make SharePoint a useable interface. Any guidance on how to resolve
these issues is greatly appreciated. This is not a branded website, and there has been no changes made to the standard interface.
Kind regards
Jarrad Koppen

I'm not sure what the easiest way is either. First, I would try to create a new site collection with a new library and see if you get the same behavior. If not, then its something in the upgrade process. If it does that also would point
to something being wrong in the way that javascript is being executed.
If it is happening everywhere I suspect you'll have to start tracing javascript using something like IE developer's toolbar to see why the status on those buttons isn't changing when you select a document. I'm not sure what else to suggest.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

SharePoint 2013 CAL and External users

Hi,
We are setting up an extranet site(SharePoint 2013 standard version) on Rackspace, Both employee and non-employee will use this site. Employee will use company existing SAML 2.0 based authentication and non-employee will use FBA to login to
the portal.
I would like to know if we need to buy CAL for external users(non-employee)? What is the definition of external users?
Thanks,
Pat

Check out this post and this should answer all you questions.
http://social.technet.microsoft.com/forums/sharepoint/en-US/0756aaa7-b307-4793-b019-bc58d4ace8b2/sharepoint-foundation-fba-on-internet-licensing
Thanks, Danny Hickman IT Support Specialist

SharePoint 2013 Enterprise and SQL Server 2012 Standard edition vs. Enterprise - feature question

I can't seem to find any clear answers to the implications of installing SQL Server 2012 standard edition vs. enterprise in regards to SharePoint 2013.
I understand that to get many of the features you need Enterprise edition of SQL 2012; but, what I can't figure out is if the backend SharePoint SQL 2012 is standard; but, the PowerPivot/SSRS server is Enterprise will we still get the features?
If we have 3 tier SharePoint farm, one of those tiers is for the SQL Server database backend. If that SQL instance is 2012 standard and we add another server to the farm w/ SQL 2012 Enterprise to handle the tabular models, PowerPivot, and SSRS in integrated
mode will we still get the features?
Or, can we (should we) install Enterprise 2012 as the SharePoint database backend and let that instance triple down as also the PowerPivot and SSRS instance?
The Degenerate Dimension

Hi MMilligan,
SQL Server 2012 Standard is not supported PowePivot for SharePoint . In addition, SQL Server 2012 Standard is also not support some Reporting Services Features.
For more information, please refer to Features Supported by the Editions of SQL Server 2012:
http://msdn.microsoft.com/en-us/library/cc645993.aspx.
Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1):
http://msdn.microsoft.com/en-us/library/jj218795.aspx.
If you have any problem, please feel free to let me know.
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support

SSRS with SharePoint 2013 Integrated and Claims

I have been reading a number of sources for SQL Server 2012 SSRS and I can't quite seem to get a straight answer about this. Does SSRS support SAML Token Claims? or does it still require the C2T conversion (which effectively requires a windows account
to work)? The reason we ask is that they have other uses for SharePoint and would prefer to not go too far outside the box with the identity provider, but still do not want to stand up an externally facing AD.

Hi Kpvuppala,
From the Reporting Services Clients do not support LiveID or SAML Claims Authentication section of the
Claims Authentication and Reporting Services document, we can see that:
The Reporting Services client applications: Report Builder, the Report Designer in Business Intelligence Development Studio, and Management Studio do not support connecting and authenticating with LiveID or SAML Claims based SharePoint Web applications.
The clients can work with other forms of Claims Authentication because they use the Reporting Services authentication endpoint. The endpoint allows the clients to communicate to SharePoint through the same components used by ASP.NET forms authentication. SAML
Claims and LiveID authentication work differently and are not supported by the Reporting Services clients.
There is no official document on this topic for SSRS 2012 and SharePoint 2013. Although it is for SSRS 2008 R2 and SharePoint 2010 products, I think it applies to SSRS 2012 and SharePoint 2013 as well. The SAML Claims authentication may not use Reporting
Services authentication endpoint still.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

SSRS 2012 integrated with Sharepoint 2013, subscription and impersonation

Hello,
We are configuring SSRS 2012 integrated with Sharepoint 2013. The reports are connecting to SSAS cubes via shared Datasources. We have defined user based roles and security in the cubes and would like to pass the effective username to the cubes when they
access data via reports.
Also we need to create subscriptions on these reports to run on either daily/weekly or monthly schedule and send email to a list of users.
How do we configure our Datasources on sharepoint so both could be acheived.
Our Database and Sharepoint are on different servers.
Thanks
Deepak

Hi Deepak
For your first question:
while configuring the datasource in SharePoint, check the option 'Set execution context to this account' in the settings. This will pass the effective user name to the cubes.
Thanks
Bala

Sharepoint 2013 workflows and Due date

hi, i'm a sharepoint designer 2010 user, and i recently migrate to sharepoint 2013 (and use sharepoint designer 2013).
I understood it was impossible to migrate sharepoint 2010 workflow to sharepoint 2013 workflows ! But it was possible to call 2010 workflow from 2013 worikflow.
However, i thought i could reproduce workflow under SPD 2013. I recently discover that was not as possible as it seems
for example, it was possible to escalate a task after due date, under SP2010 workflow. I try to reproduce it under sharepoint 20103 workflow, but it seems not to be possible any more (i read this article >>
link <<!
Does any sharepoint's expert can confirm it to me !?
Mon blog : http://spinfopath2010.blogspot.fr/ Sharepoint online 2010 Sharepoint Designer 2010 - InfoPath 2010 - newbie level !

Also please note that you can combine both workflow engines together! It means you can create 2013 workflow using the new model and if you face any action which is no longer available (and you cannot find any other way, e.g. impersonation step) -
you are able to just easily invoke 2010 workflow with its set of actions.
To do so, please read following article, which also describes why some features are no longer available and how to implement these deprecated activities in 2013 environment:
http://msdn.microsoft.com/en-us/library/jj728659.aspx
Hi martin,
Yes, i know i can call a 2010 worklfow from a 2013 one, but it seems to me "tricky", and not a very good practice. Because, these workflows can be either deprecated or abandonned.
I prefered to use a "full" 20130 workflow instead of mixing it with an older version
Anyway, if there is no other way, i'll do it
Mon blog : http://spinfopath2010.blogspot.fr/ Sharepoint online 2010 Sharepoint Designer 2010 - InfoPath 2010 - newbie level !

SharePoint 2013 Templates and OneNote

Hello,
I created a sub site the exact way that I wanted it so I created a template. When I create a new sub site with this template everything works OK but OneNote. I receive the following error when I try to open it in a browser.
Sorry, something went wrong
Item does not exist. It may have been deleted by another user.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: ceb38c9c-82b3-3026-cf47-fd5cb9a33d10
Any ideas as to why? If I create a sub site and pick the team site template it works fine but then I have to add all the other stuff in manually.

I have experienced this quite a number of times now and am still searching for an ultimate fix. However this is what I currently do to solve this:
1. Best thing is to not have Site Notebook Feature enabled (Wheel Menu>Site Settings>Manage Site Features) when initially pulling the Site Template. If you are able to do this, you can skip down to #4 below after you create your new Site using the
Site Template.
2. If you can't disable the Site Notebook Feature in the source Site you pull the Template From, then once the new Site that you created using the Site Template is up, disable Site Notebook on the new Site.
3. Locate and Delete the Notebook file which will still have the name of the source Site that you pulled the Site Template from. In my case that is located in the Site Assets container (Wheel Menu>Site Contents>Site Assets).
4. Re-enable the Site Notebook Feature (Wheel Menu>Site Settings>Manage Site Features). This last step creates a new Site Notebook file which is correctly named and linked for your newly created Site.
Maybe you already know this, but System Accounts can not view anything that is rendered by Office Web Apps server in SharePoint. So, if you are doing all of this using a System Account, even after following all of the steps above, you cannot view the new
Site Notebook unless you login to the new Site as some account besides System Account.
Just for additional info, here is a link to an article I found some time ago that also discusses this problem:
http://sergeluca.wordpress.com/2013/09/02/sharepoint-2013-save-as-a-template-notebook-bug-and-composed-look-bug/

If statement formula in Sharepoint 2013 returns and error

Similar Messages

Maybe you are looking for