PROPERTY NOT WORK

DEAR ALL
GOOD MORNING
A RIDO_BUTTON
IN TRIGGER WHEN VILDATE ITEM
I WRITE THTIS CODE BUT NOT WORK
SET_ITEM_PROPERTY('XXX',VISUAL_ATTRIBUTE,CURRENT_ROW_BACKGROUND_COLOR,'VISUAL_RED');
WHAT IS CORRECT
THANK YOU ALL

Re: PROPERTY NOT WORK

Similar Messages

Result Type Condition for Multi value Manage Property not working

Hi All,
I have created one template & I wanted to show this template on particular condition. So I created the result type. The Managed property (MP) that I used, I have verified its attributes all attributes are selected and its type is Multi value. I am trying
to apply the "Show fewer conditions" and some how the value not matched.
I have checked MP ; it has all the values but some how the template not called. When I removed this condition it working and when choose other MP other then Multi valued. It is working as expected.
Please let me know if i miss something here.
PS: I have checked each option from the Query drop down like "Equals any of" and "Contains any of" not working in case of multi value attribute. Please help.
I have explain this issue more details in this post : http://sharepointfordeveloper.blogspot.com/2015/02/sharepoint-search-2013-result-type-with.html
Regards,
Basant Pandey
http://sharepointfordeveloper.blogspot.com

Update on above mentioned issue.
I have verified the same at my end. So I come to this conclusion this is product issue. Either need to raise the ticket to Microsoft related to this issue.
Regards,
Basant Pandey
http://sharepointfordeveloper.blogspot.com

Flex 4 ToggleButton selected property not working

I am trying to set a FlexToggle buttons selected property by state value and it does not work. It only works when I click on the button.
<buttons:MaxRestoreToggleButton id="resizeWindowButton" selected="false" selected.maximized="true"/>
any ideas?

Well I am creating a ToggleButtonSkin and yes, I am calling the invalidateSkinState(); but it still doesnt seem to be working.
<?xml version="1.0" encoding="utf-8"?>
<s:ToggleButton xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
toolTip="Maximize"
width="20" height="20"
skinClass="tat.skins.buttons.MaxRestoreToggleButtonSkin" change="{trace('hi');}"
>
<s:states>
<s:State name="up" enterState="{invalidateSkinState();}"/>
<s:State name="over" stateGroups="overStates" enterState="{invalidateSkinState();}"/>
<s:State name="down" stateGroups="downStates" enterState="{invalidateSkinState();}"/>
<s:State name="disabled" stateGroups="disabledStates"/>
<s:State name="upAndSelected" stateGroups="selectedStates, selectedUpStates" enterState="{invalidateSkinState();}"/>
<s:State name="overAndSelected" stateGroups="overStates, selectedStates" enterState="{invalidateSkinState();}"/>
<s:State name="downAndSelected" stateGroups="downStates, selectedStates" enterState="{invalidateSkinState();}"/>
<s:State name="disabledAndSelected" stateGroups="selectedUpStates, disabledStates, selectedStates" />
</s:states>

<fx:Metadata>
[SkinState('up')]
[SkinState('over')]
[SkinState('down')]
[SkinState("disabled")]
[SkinState('upAndSelected')]
[SkinState('overAndSelected')]
[SkinState('downAndSelected')]
[SkinState("disabledAndSelected")]
</fx:Metadata>
<fx:Declarations>
</fx:Declarations>
<fx:Script>
<![CDATA[
]]>
</fx:Script>
</s:ToggleButton>
<?xml version="1.0" encoding="utf-8"?>
<s:SparkSkin xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark"
    xmlns:fb="http://ns.adobe.com/flashbuilder/2009" minWidth="21" minHeight="21" alpha.disabledStates="0.5" >
    
    <fx:Metadata>
    <![CDATA[
        [HostComponent("tat.components.buttons.MaxRestoreToggleButton")]
    ]]>
    </fx:Metadata>
    <fx:Script fb:purpose="styling">
[Bindable]public static var glowColor:uint = 0xFFFFFF;
[Bindable]public static var backgroundColor:uint = 0xFFFFFF;
/* Define the skin elements that should not be colorized.
           For toggle button, the graphics are colorized but the label is not. */
        static private const exclusions:Array = ["labelDisplay"];
         * @private
        override public function get colorizeExclusions():Array {return exclusions;}
         * @private
        override protected function initializationComplete():void
            useChromeColor = true;
            super.initializationComplete();
         * @private
        override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number) : void
            super.updateDisplayList(unscaledWidth, unscaledHeight);
        private var cornerRadius:Number = 2;
    </fx:Script>
    
    <s:states>
        <s:State name="up" enterState="{this.hostComponent.toolTip='Maximize' }"/>
        <s:State name="over" stateGroups="overStates" enterState="{this.hostComponent.toolTip='Maximize'}"/>
        <s:State name="down" stateGroups="downStates" enterState="{this.hostComponent.toolTip='Maximize'}"/>
        <s:State name="disabled" stateGroups="disabledStates"/>
        <s:State name="upAndSelected" stateGroups="selectedStates, selectedUpStates" enterState="{this.hostComponent.toolTip='Restore'}" />
        <s:State name="overAndSelected" stateGroups="overStates, selectedStates" enterState="{this.hostComponent.toolTip='Restore'}"/>
        <s:State name="downAndSelected" stateGroups="downStates, selectedStates" enterState="{this.hostComponent.toolTip='Restore'}"/>
        <s:State name="disabledAndSelected" stateGroups="selectedUpStates, disabledStates, selectedStates" />
    </s:states>
    
<s:Rect id="bg" left="0" right="0" top="0" bottom="0" radiusX="2">
<s:fill>
<s:SolidColor color="{backgroundColor}" alpha=".1"/>
</s:fill>
</s:Rect>
<s:Rect id="glow" left="-1" right="-1" top="-1" bottom="-1" radiusX="2">
<s:fill>
<s:SolidColor color="{glowColor}" alpha.up="0" alpha.selectedUpStates="0" alpha.overStates=".5" alpha.downStates=".2" alpha.disabled="0"/>
</s:fill>
</s:Rect>
<s:BitmapImage source.selectedStates="@Embed('../../../assets/images/windows_16.png')" source="@Embed('../../../assets/images/windows_window_16.png')"
   horizontalCenter="0" verticalCenter="0"/>
</s:SparkSkin>

Enable Property Not working in Form Personalization- R12

Hi All,
I have an requirement to grade out the button item for Production Supervisor- Batch details, The Button Item is Transact Material, This Button should be grade out always for this particular responsibility.
See below what logic i used for this requirement in Form Personalization.
1. For the Batch Details Form Created one Personalization with trigger condition WHEN-NEW-BLOCK-INSTANCE and processing mode Not in Enter-Query Mode.
2. In Actions tab - Type : Property
Object Type : Item
Target Object: GME_BATCH_HEADER.TRANSACTIONS
Property Name: ENABLED
Value : FALSE
After i validate it and pressed APPLY NOW- only at that time the "Transact Material" Button showed as Grade out but after i closed the personalization window and reopen the Batch Details form and am seeing that Transact Material still Enabled instead of Grade out.
I prefectly saved the personalization window.
I dont knw why it is working only when i see preview(APPLY NOW) option and not working once i reopen the batch details or logout the apps and reloged again still having the same issue.
Please help me out if any one come accross this type of issue.
welcoming your comments on this...
Regards
Prabu

Are you making the fields "required" using personalization?
The Raise FTF action won't produce any message.
It looks like some other code is firing before your personalization fires.
It seems user is unable to save the record. So your requirement is achieved.
If not, please post details of the personalization.
Sandeep Gandhi

BEx Analyzer report "New Formula", "Scaling Factor" property not working

Hi Experts,
I have created a New Formula(Ex:- Dispatches * 2) in BEx Analyzer report. The result of the "New Formula" is 2000. When I maintain Scaling Factor as "1000" to the New Formula properties, the result should be 2 but here 2000 is coming again.
When I maintain this property to the existing keyfigure in Analyzer report, it is working fine.
Please help me in this whether Scaling Factor can be applied to the New Formula or not in BEx Analyzer report. If it works, what changes we have to make to the New formula.
SAPKW73010 is applied already to SAP BW-730
Please see the attachment.

Sree,
Is the variable ABC the new one that you've created with Scaling factor setting given? The message you get on doing a syntax check on the query indicates that settings are ignored for use beyond the query.
And if this is the case, this is a known issue.
However such settings will work on existing keyfigures as it is in your case.
What you can hence do for this new variable is that if you are developing reports on top of this bex query, you can make the scaling factor setting at the report level.
Let me know if this works for you.
Regards,
Srilakshmi B

Alpha property not working on TextField when publish for Reader 9

Hi,
I have a movie that is working fine when I publish for Reader 10, but when I publish for Reader 9, the code that assigns an alpha property to my TextFields stops working. I have a previous movie, which I probably did in CS4, that uses similar code to fade in and out TextFields. It was published for Reader 9 and works fine.Is it possible that something has changed in CS5 (note, I'm not using TLF text boxes, only dynamic TextFields)?
Here's an example of the code I'm using:
stop();
import fl.transitions.Tween;
import fl.transitions.TweenEvent;
import fl.transitions.easing.*;
import flash.events.*;
import flash.text.*;
import flash.text.TextFormat;
import flash.utils.Timer;
import flash.display.MovieClip;
import flash.display.Sprite;
var txtFormat1:TextFormat = new TextFormat();
txtFormat1.font = "Optima";
txtFormat1.color = 0x000000;
txtFormat1.bold = false;
txtFormat1.size = 16;
txtFormat1.leading = 2;
var subtitle:TextField = new TextField();
subtitle.autoSize = TextFieldAutoSize.CENTER;
subtitle.selectable = false;
subtitle.defaultTextFormat = txtFormat1;
var fadeInSubtitle:Tween;
addChild(subtitle);
subtitle.x = stage.stageWidth / 2 - subtitle.width / 2;
subtitle.y = stage.stageHeight / 2 - subtitle.height / 2;
subtitle.alpha = 0;
subtitle.text = "What is the most important question in";
fadeInSubtitle = new Tween(subtitle,"alpha",None.easeNone,0,1,3,true);

Thanks.
Just curious: Is there a reason why the alpha on the TextFields worked without embedding fonts when publishing for Flash Player 10? Does it handle text, even when it's not TLF, differently than Flash Player 9?

[CS3] FL 3.0 - AS2: _parent property not working!

Hey Guys,
I am not able to access the functions and variables of a parent SWF from a loaded SWF using the _parent notation in FlashLite 3.0 - AS2.
Check the attachment.... I have attached the source files. Please unzip them and check that when you publish the parent.fla it loads the child.swf via a loadMovie() and then at the last frame of child.swf I have tried to access some property and method from parent.swf using _parent and I am not able to do so......
Can somebody tell me why this is happening and what is the workaround for this!
As ever,
Vinayak Kadam

Your parent swf needs to allow access for scripting by the child. Read the Flash 8 security documentation for the full details on this.
To solve it you should use system.security.allowDomain("*")
Mark

Setting nonProxyHosts property not working

How do you set the nonProxyHosts property for Jrockit 1.5.0_11. We are trying to set this property for Aqualogic ESB which is using Jrockit by setting this property in net.properties under Jrockit but it does not seem to honor it. It seems to pick up proxyHost property though.

Well the issue is when I run the installSvc.cmd to install Aqualogic as a service and I am setting environment variable JAVA_OPTIONS with -DnonProxyHosts with a pipe (|) delimited list (e.g host1|host2|host3), but the script barfs and I think it does not like pipe symbol. May be this is more of a Aqualogic question than a JRockit one, or may be a windows script. Do you know if I need to escape the pipe symbol somehow? I tried escaping it with ^ but that did not help.

Visible Property Not Working

Hello,
I have a button, that when rolled over, will show another
sprite.
Code on the button:
on beginSprite
sprite("print01").visible=FALSE
end
on MouseEnter me
_player.cursor(280)
sprite(me.spriteNum).member=member("01_btn_o")
sprite("print01").visible=TRUE
end
on MouseLeave me
_player.cursor(0)
sprite(me.spriteNum).member=member("01_btn_n")
sprite("print01").visible=FALSE
end
And the "print01" sprite has been named and is on the
timeline.
I keep getting an error message saying the property isn't
found #visible
Any help would be great - thanks

> I keep getting an error message saying the property
isn't found #visible
My guess is you misspelled the sprite name, either in the
script or on the
sprite itself. That's the error you get when trying to access
a
non-existent sprite. (Yeah, I know, not a very helpful error
message there.
I wish it would just say "no such sprite" instead - I've been
hit with that
one more times than I care to count.)
I know you solved it by using the sprite's number instead of
its name, but
since the addition of the sprite-naming feature, I've tried
to get out of
using sprite-numbers, because if you ever need to move your
sprites around
on the score (say, to put something underneath them), you
then have to edit
all your code that refers to numbers to make them match
again, which can be
a real hassle on larger projects.

DAQmx Channels To Read Property Not Working

I have an AI task configured with multiple channels and then set the Channels To Read property to the channel I want before calling the Read VI. If the Channels To Read property value that I set matches the value that was previously set the task passes all the channels to the Read VI rather than the single channel of the property. Does anyone have insight into what might be the problem?

Hi, I'm using Labview 8.2 and DAQmx 8.8. I have attached screenshots of the code.
Attachments:
Post1.PNG ‏40 KB
Post2.PNG ‏27 KB

After upgrading to 10.7.5 some of my AU plugins can not be validated in Logic pro. (I got error message "Remove property listener". I can not work anymore. What should I do?

After upgrading to 10.7.5 some of my AU plugins can not be validated in Logic pro. (I got error message "Remove property listener". I can not work anymore. What should I do?
VIBAC

I downloaded and installed
OS X Lion 10.7.5 Supplemental Update
and that solved my problem completely. (368 AU plugins now works!)

In SSRS , after exporting report in excel,wrap text property for cell and freeze column for SSRS table header not working in Excel

I am working no one SSRS my table headers are freeze cangrow property is false and my report is working perfect while rendering data on RDL and i want same report after exporting in Excel also , i want my table header to be freeze and wrap text property
to work after exporting in my report in excel but its not working ,is there any solution ? any patch ? any other XML code for different rendering ?

Hi Amol,
According to your description, you find the wrap text property and fix column is not working after exporting into Excel. Right?
In Reporting Services, when exporting to excel file, it has limitation for textbox.
Text boxes are rendered within one Excel cell. Font size, font face, decoration, and font style are the only formatting that is supported on individual text within an Excel cell.
Excel adds a default padding of approximately 3.75 points to the left and right sides of cells. If a text box’s padding settings are less than 3.75 points and is just barely wide enough to accommodate the text, the text may wrap in Excel.
In this scenario, it supposed to be wrap text unless you merge cells. If cells are merged, word-wrap does not work correctly. If any merged cells exist on a row where a text box is rendered with the
AutoSize property, autosize will not work. For the Fix Data Property, it can't be working in Excel. These are features when exporting to Excel. We can't change it because it's by design.
Reference:
Exporting to Microsoft Excel (Report Builder and SSRS)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

ValueChangeListener is not working.for disable property

valueChangeListener is not working for disable property with following details. Requirement is to enable to date if from to date is entered.
Field 1:
<af:inputDate value="#{bindings.PrintFromDate.inputValue}"
label="#{bindings.PrintFromDate.hints.label}"
required="#{bindings.PrintFromDate.hints.mandatory}"
shortDesc="#{bindings.PrintFromDate.hints.tooltip}"
id="id2" autoSubmit="true"
*valueChangeListener="#{reprintBean.enableToDate}">*
<f:validator binding="#{bindings.PrintFromDate.validator}"/>
<af:convertDateTime pattern="#{bindings.PrintFromDate.format}"/>
</af:inputDate>
<af:inputDate value="#{bindings.PrintToDate.inputValue}"
label="#{bindings.PrintToDate.hints.label}"
required="#{bindings.PrintToDate.hints.mandatory}"
shortDesc="#{bindings.PrintToDate.hints.tooltip}"
id="id1"
*disabled="#{!requestScope.enableToDate}"*
*partialTriggers="id2"*>
<f:validator binding="#{bindings.PrintToDate.validator}"/>
<af:convertDateTime pattern="#{bindings.PrintToDate.format}"/>
</af:inputDate>
public void enableToDate(ValueChangeEvent valueChangeEvent) {
System.out.println("IN enableToDate");
if (valueChangeEvent.getNewValue() != null) {
FacesContext context = FacesContext.getCurrentInstance();
System.out.println("Enable to Date");
context.getExternalContext().getRequestMap().put("enableToDate",true);
Please suggest me what is wrong on this.
Edited by: SrinivasA on Jan 28, 2011 5:34 PM

I still not able to achive this. (null the to date value if the FromDate has changed)
<af:inputDate value="#{bindings.PrintFromDate.inputValue}"
label="#{bindings.PrintFromDate.hints.label}"
required="#{bindings.PrintFromDate.hints.mandatory}"
shortDesc="#{bindings.PrintFromDate.hints.tooltip}"
id="id2" autoSubmit="true"
*binding="#{reprintBean.fromDate}"*
*valueChangeListener="#{reprintBean.enableToDate}"*>
<f:validator binding="#{bindings.PrintFromDate.validator}"/>
<af:convertDateTime pattern="#{bindings.PrintFromDate.format}"/>
</af:inputDate>
<af:inputDate value="#{bindings.PrintToDate.inputValue}"
label="#{bindings.PrintToDate.hints.label}"
required="#{bindings.PrintToDate.hints.mandatory}"
shortDesc="#{bindings.PrintToDate.hints.tooltip}"
id="id1"
disabled="#{bindings.PrintFromDate.inputValue eq null}"
binding="#{reprintBean.toDate}"
*partialTriggers="id2">*
<f:validator binding="#{bindings.PrintToDate.validator}"/>
<af:convertDateTime pattern="#{bindings.PrintToDate.format}"/>
</af:inputDate>
Value change method:
public void enableToDate(ValueChangeEvent valueChangeEvent) {
*setToDate(null);*
This method is not able to reset the to date value to null. Please help to find the issue here.
Edited by: SrinivasA on Feb 1, 2011 5:12 PM

Silverlight 5 binding on a property with logic in its setter does not work as expected when debug is attached

My problem is pretty easy to reproduce.
I created a project from scratch with a view model.
As you can see in the setter of "Age" property I have a simple logic.
public class MainViewModel : INotifyPropertyChanged
public event PropertyChangedEventHandler PropertyChanged;
private int age;
public int Age
get
return age;
set
/*Age has to be over 18* - a simple condition in the setter*/
age = value;
if(age <= 18)
age = 18;
OnPropertyChanged("Age");
public MainViewModel(int age)
this.Age = age;
private void OnPropertyChanged(string propertyName)
if (this.PropertyChanged != null)
PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
In the MainPage.xaml
<Grid x:Name="LayoutRoot" Background="White">
<TextBox
Text="{Binding Path=Age, Mode=TwoWay}"
HorizontalAlignment="Left"
Width="100"
Height="25"/>
<TextBlock
Text="{Binding Path=Age, Mode=OneWay}"
HorizontalAlignment="Right"
Width="100"
Height="25"/>
</Grid>
And MainPage.xaml.cs I simply instantiate the view model and set it as a DataContext.
public partial class MainPage : UserControl
private MainViewModel mvm;
public MainPage()
InitializeComponent();
mvm = new MainViewModel(20);
this.DataContext = mvm;
I expect that this code will limit set the Age to 18 if the value entered in the TextBox is lower than 18.
Scenario: Insert into TextBox the value "5" and press tab (for the binding the take effect, TextBox needs to lose the focus)
Case 1: Debugger is attached =>
TextBox value will be "5" and TextBlock value will be "18" as expected. - WRONG
Case 2: Debugger is NOT attached =>
TextBox value will be "18" and TextBlock value will be "18" - CORRECT
It seems that when debugger is attached the binding does not work as expected on the object that triggered the update of the property value. This happens only if the property to which we are binding has some logic into the setter or getter.
Has something changed in SL5 and logic in setters is not allowed anymore?
Configuration:
VisualStudio 2010 SP1
SL 5 Tools 5.1.30214.0
SL5 sdk 5.0.61118.0
IE 10
Thanks!

Inputting the value and changing it straight away is relatively rare.
Very few people are now using Silverlight because it's kind of deprecated...
This is why nobody has reported this.
I certainly never noticed this problem and I have a number of live Silverlight systems out there.
Some of which are huge.
If you want a "fix":
private void OnPropertyChanged(string propertyName)
if (this.PropertyChanged != null)
//PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
Storyboard sb = new Storyboard();
sb.Duration = new Duration(new TimeSpan(0, 0, 0, 0, 100));
sb.Completed += delegate
PropertyChanged(this, new PropertyChangedEventArgs(propertyName));
sb.Begin();
The fact this works is interesting because (I think ) it means the textbox can't be updated at the point the propertychanged is raised.
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML

Get-Hotfix InstalledOn property not returning hotfix installed Date and Time on Windows Server 2008 SP2 but works on Windows Server 2008 R2 SP1

Hi,
I am working on a validation script to get the list of hotfixes installed on Domain Controllers every month as part of our monthly DC patching process. I have been successful in getting these details for DC's with (Windows Server 2008
R2 SP1, Powershell v2.0) using the below command.
Get-HotFix -cn $computer | Select-Object PSComputerName,HotFixID,Description,InstalledBy,InstalledOn | where InstalledOn -ge (Get-Date -Day 1 -Format d) | FT -AutoSize
I execute the above from a jump box with powershell v4.0 (Server 2008 R2)
However, when I try the same command from the jump box to query DC's with (Server 2008 SP2, powershell v2.0). It doesn't return the InstalledOn date and time. It was giving error for the InstalledOn property and hence I renamed it to $_.InstalledOn. Now
I don't get error but still no details displayed for InstalledOn property.
I tried using the below, as could see on few forums that this might resolve the issue. I also tried removing the "where" part but still no installation date returned.
Get-HotFix -cn $computer | Select-Object HotFixID, Description, InstalledBy, @{l="InstalledOn";e={[DateTime]::Parse($_.psbase.properties["installedon"].value,$([System.Globalization.CultureInfo]::GetCultureInfo("en-US")))}}
| where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize
Have tried this locally on the 2008 SP2 DC but still not working. Please advise what is going wrong?
Note: If I execute the below command locally on the 2008 SP2 DC, I am getting the InstalledOn output. However, when executed from the jump box with powershell v4.0 (Server 2008 R2) to query
the same 2008 SP2 DC, it just gives the prompt again without any error or output. This behavior is consistent for other 2008 SP2 DC's in the environment.
Get-HotFix -cn $computer | Select-Object HotfixID,Description,InstalledBy,InstalledOn | where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize

Hi jrv, I have already tried the Win32_QuickFixEngineering option, which doesn't work either. Apologies for not mentioning the workarounds that I have already tried.
Get-Hotfix seems to be just a wrapper for Win32_QuickFixEngineering as per the below article. (http://technet.microsoft.com/en-us/library/hh849836.aspx)
I have seen a mention of using the WU ActiveX control on few forums, but was too lazy to read it through.
After rigorous testing, it makes me realize that somewhere the Get-Hotfix dates formatting\comparison isn't working.

PROPERTY NOT WORK

Similar Messages

Maybe you are looking for