I am confused with this feature in CRM13, please help.
In CRM11,
I added some options in the "StatusReason" field for "Inactive".
When i try to deactivate that record from the grid, it will ask you to select the status for deactivation.
When i try to deactivate the record from the form itself, then also same thing happened.
Now my CRM upgraded to CRM13.
In CRM13 ,
deactivation of record from grid will allow you to select the status that is added for the "Inactive" but,
deactivation of record from the form itself, will not allow you to select the status that is added for the "Inactive" rather than this, it will deactivate the record automatically.
Is there any big change happened in this CRM13 for this feature?
Any kind of idea will be appreciated. Thanks in advance.
Thanks,
Anish
I had the similar experience when deactivating the record from form level. There is no MSDN CRM article related to this. CRM 2013 brand new menu is designed to ease user navigation, free up screen space, remove pop-up windows, etc. Probably part of this strategy this feature has been depreciated. There is nothing being mentioned in CRM Rollup 13. http://support.microsoft.com/default.aspx?kbid=2891271.
The workaround is to hide the deactivate button and make a custom button to invoke a dialogue to set the relevant status reasons.
This was a bug in my CRM Online instance.
Now automatically this has been fixed.
I do not know how this is fixed..but I guess after some updates..this got fixed.
Related
I'm a bit new in Teamstudio xcontrol ( a bootcard based UI for xpage ) and i'm wondering if there is a property or a function that allows deleting of documents. I checked the FormViewer Custom control, FormEditor and any custom control that is related to domino documents or view but I haven't found any. I also checked the website of the xcontrol but I haven't found any. Do I miss something or do we really need to create the functionality on our own. Thanks in advance for the help!
They're isn't, however in the upcoming version 1.2 we do support the addition of custom buttons so you could add your own delete button.
Unable to understand why does Update Panel does do the soft post back (partial post back).
Nothing happens on page after the dropdownlist selected Index change.
tried to ref :http://msdn.microsoft.com/en-us/library/ff650218.aspx
Would be thankful if any already cracked up the isse for SharePoint 2013.
request is processed on dropdown change without any exception but does not reflects UI
you should check your trigger, perhaps you dont have it, or its not referencing the control properly
take a look here, and if you need, make a post over there
https://sharepoint.stackexchange.com/questions/110432/sharepoint-2013-webpart-timer-not-tick/110436#110436
I have stumbled across another problem after doing a successful migration. On one of the list, there are some missing fields when you go to edit an item. these same fields show up when you go to view an item. I do not recall hiding any fields and with with only two of 25 fields not showing is puzzling. Any ideas in the programming world as to what may have taken place?
Are you migrating code from 2007 to 2010? If so, you should look at these views in SharePoint Designer. You should have the ability to create a new View (with the desired fields), make it default and omit the older view.
I am guessing that the 2010 upgrade is a red herring and in fact whaat has happened is that
You've modified the edit form using SharePoint Designer (SPD) thereby 'fixing' the fields to those in place at that time.
You've later added some extra fields.
These will appear on the View as that wasn't edited and 'fixed' but not edit.
I have a SharePoint Designer workflow like the following: (just an example)
If ActionId equals 1
Email InfopathForms:Customer Email
Sometime later, it changes itself to the following:
If field equals 1
Email InfopathForms:
Where the field ActionId is lost and the Customer Email is lost too. Also in the email body, all the Lookup fields are also lost...
Has anyone had this problem before...?
This has happened like 6-7 times already... If anyone know a solution to fix it please let me know... much appreciated!!!!!!!!!!!!!!!
And is there some way to backup the workflow...? So I can easily restore it after it resets itself..?
sharepoint designer is not the most useful tool for developing and deploying workflows. I have not experieced this problem. Somthing simliar when two dev's were attacking the same list with sharepoint designer. could this be your problem?
I've noticed similar symptoms when variable names change... Is your InfoPath form changing? Or are the promoted fields changing? If so, I would expect this behavior. Simple fix is to update the variables in the workflow step, and then leave the InfoPath form alone. :D
We have the same issue.
I found that the lookup fieldname in the xoml file is diffrent if you re-link (pick) it.
An example: FieldName="WFOrder_x0020_Type" after re-link it is FieldName="WFOrder_x0020_Type0"
<ns0:LookupActivity ListId="{}{8FC10225-9397-4F5A-88B6-FE4C37A44970}" x:Name="ID645" FieldName="**WFOrder_x0020_Type**" LookupFunction="LookupFriendlyString" __Context="{ActivityBind ROOT,Path=__context}" ListItem="{ActivityBind ROOT,Path=__item}">
I open the xoml file in textpad and edit all the fields by adding the zero into the fieldname. Saved it and my workflow is working again.
Just to clarify, I did modify the InfoPath form and published it, where after my workflow lookup fieldnames got messed up.
Situation:
A custom "Master Document" content type inherits from Document
The "Master Document" content type has five additional choice fields
There are five custom "Document Template" content types that inherit from the "Master Document" content type
Each of the "Document Template" content types uses a different Word document template (.dot) file
Each of the "Document Template" content types have been added to a document library
Problem:
I click on a document in the library
Document opens up in Word 2003 for me to edit
I make some changes and save
A box pops up called "Web File Properties". The window contains all of my custom metadata properties and the ContentType field. The ContentType field is set correctly to the current content type. The other fields are reset to their default values. This same window can apparently be opened by going to File -> Properties
This window by itself would be fine except for two reasons:
It includes the ContentType column
All of my custom metadata properties are visible but are reset to their default values instead of whatever values were previously selected. This means, every time the user wants to save the document, they have to remember what properties were tagged and set them back.
Question:
Can I disable this Web File Properties box?
If no... can I get the fields that show up to be populated to their correct values?
If no... is there a way to disable my fields from displaying in this window?
If no... is this a SharePoint page that I can modify?
***Edit with some more information***
It looks like this only happens in Office 2003 and looks like it affects Choice fields. If I create the same column as a Lookup field, it seems to work.
Edit again
Looks like if the lookup field is a multi-select field then it will not show up in the Web File Properties box at all (single select lookups still work).
edit 10/14/2009
Link to the KB Article mentioned below by Brenda:
http://support.microsoft.com/kb/971500/
This is more of a workaround rather than an answer but I figured I might as well put it here in case it helps someone else.
It seems as if these issues with the Web File Properties box is specific to Office 2003. The issues I reported above seem to be fixed in Office 2007.
If you want to get it working in 2003 and you have choice/lookup fields in your Document content type, here is the summary:
Single select Choice fields DO NOT work
Multi select Choice fields DO work
Single select Lookup fields DO work
Multi select Lookup fields DO NOT work
FYI - I want to CORRECT my previous post. The fix DID FIX my problem after I deleted my internet cache. Works PERFECT now. Here is the KB you need: KB971500 I can email you the fix if you can't find it. The notes in the document do not describe the problem exactly as I would have, but it was the fix for my case.
bhartson#lbrealty.com
We have the EXACT problem. I've opened a case with Microsoft back in February and they were able to finally duplicate my problem.
I have been kept informed and told that my fix would be available with the JUNE cumulative upates. I just received a specific hotfix from my Microsoft rep and applied it and it still did NOT fix my problem. I am hoping he gave me the wrong one and has the real one to send me.
Thanks for your post. I'm may try some of your suggestions above but I just want Microsoft to fix this. We can't upgrade to Office2007!
Thanks.
man, this was really killing me, I spent an entire day recreating document libraries and all sorts of content-types and variations of my excel template before I figured this was a bug... At least MS has a little hotfix request thing now... they're going to send it to me I guess :\
I didn't test this in excel/office 2003 and really botched a presentation of our little workflow... embarassing... always test with the app & environment people are going to use!!!
thanks for the KB article number