LinkToURL reference property a little short

Hi
I pasted in a SDN URL into the reference porperty of a LinkToURL UI element and discovered that it got truncated at about 128 characters
Perhaps the size of this property should be increased
Peter

Hi,
Create a context attribute. URL type string.
bind this attribute to the refernce property of the link to URL.
In wddoint write the below code:
data lv_url type string.
lv_url = 'ur sdn url'.
wd_context->set_attribute( name = 'URL' value = lv_url ).
Regards,
Madhu

Similar Messages

  • WebDynpro : Reference property of "LinkToURL" control

    HI All,
    I have a portal called portal1. I have a view in my WD application which has view which contains a "LinkToURL" control. There is a "reference" property that takes a URL and opens another application in a new window.
    What do I need to put as the value of this "reference" property so that it access a application running on another portal (portal2). My portal2 is on another machine in the same network.
    For example if the "reference" property of my control on portal1 is https://portal.mycompany.com/test/encrypt.html
    then how do I change this "reference" property of my LinktoURL control on portal1 so that it gets the same application from a different machine/portal (portal).
    do I need to preceede the IP address in this property.
    plz suggest
    /sab

    Hi,
       According to Armin suggesion I created calculated
    attribut(first i created one value attribute in name of calculate and set calculated property to true and ser read only to true)in context of component controller.
    I added following code in getter method .
    public java.lang.String getOutputCalculate(IPrivateBirthDayAppCust.IOutputElement element)
        //@@begin getOutputCalculate(IPrivateBirthDayAppCust.IOutputElement)
         return element.getAttributeAsText("BirthDayAppModel.Zbirthday_List.Email_Id");
        //@@end
    Under Outputput model node I created calculate value attribute.My component Context node structure is like
    this.
    Context->OutPut(Model Node)->Birthdaylist(Model Node)->Email_Id (Model Attribute).
    I am mapping Component Context to View context(Result View).My view context Structure is like.
    Context->Birthday(Model Node)->Birthdaylist(Model Node)->
    Email_Id.calculate attribute created under Birthday.
    when i am running application i got nullpointer exception.
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.bajaj.auto.wdp.IPublicBirthDayAppCust$IOutputElement.wdGetObject(IPublicBirthDayAppCust.java:472)
        at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:887)
        at com.bajaj.auto.BirthDayAppCust.getOutputCalculate(BirthDayAppCust.java:151)
        at com.bajaj.auto.wdp.InternalBirthDayAppCust.getOutputCalculate(InternalBirthDayAppCust.java:155)
        at com.bajaj.auto.wdp.IPublicBirthDayAppCust$IOutputElement.wdGetObject(IPublicBirthDayAppCust.java:474)
        ... 75 more
    Thanks & Regards
    muna

  • VI Reference Property Node inside sub-vi

    Hey Folks,
    I was always curious about why this is:
    If I open a vi-reference in one vi, and pass the reference to a sub-vi, I can put a property node in the sub-vi and get all properties just fine - as long as I am in debug mode.  When I compile to an executable this problem has its own error message and everything.  So why does debug mode not throw an error too?  I'm just trying to deduce what the heck is the difference.
    Check my painstakingly time-consuming example.
    -Devin
    I got 99 problems but 8.6 ain't one.
    Attachments:
    OpenMyReference.zip ‏42 KB

    When I discovered this issue I was coding an "About" modal screen that a user could select from a run-time menu.  This was supposed to work just like Labview's "Help->About Labview" screen, giving program description and version information.  So I tried to simply link in the revision from my vi's proerties because that would automatically keep a revision count and I didn't care what the format was as long as I could get a number.  I just wanted an easy way to check the revision, and its easy to give someone simple instructions to check the "about" screen.  Is there an easy way for a user to check the revision if all I do is put it in the application builder?  User-friendliness is key, because for me to support the application I will need to have them tell me the revision they are using over the phone or in an email.
    Will it be possible to create this screen in 8?  If I just do it in the application builder, is there any way to link to it and build an "About" screen?  I don't really care what format.  It could be revision 728 as long as a user can get to it in a simple way.  Otherwise I will have to just build a screen with plain text on it and edit the text by hand every time I build an application.  Isn't there a more elegant way to do it?
    Message Edited by billings11 on 10-20-2005 11:28 AM
    -Devin
    I got 99 problems but 8.6 ain't one.

  • Error dialog and message when SCA reference property saved in EM

    In using EM to set the value of an SCA property on a composite reference instance -- the "TARGET_DIRECTORY" SCA property which is created by the File Adapter wizard when LogicalDirectory is specified and the token name "TARGET_DIRECTORY" is specified, I get an error dialog when saving the change:
    Error performing the operation. Please view the log file for details.
    The actual property value update is made even though there is an error dialog.
    This is the corresponding server log message (note reference to JCA property LogicalDirectory in the trace -- not the property actually modified in EM):
    Message Level     1
    Component     soa_server1
    Module     RMI
    Host     eavlab56
    Host IP Address     10.47.128.181
    User     <WLS Kernel>
    Thread ID     [ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'
    Message     RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.setAttribute(Ljavax.management.ObjectName;Ljava.rmi.MarshalledObject;Ljavax.security.auth.Subject;)
    javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: Update failed, unknown property: LogicalDirectory.
    javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: Update failed, unknown property: LogicalDirectory
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:856)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:869)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:768)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:699)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.setAttribute(JMXContextInterceptor.java:234)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.setAttribute(SecurityInterceptor.java:358)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.setAttribute(WLSMBeanServer.java:294)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9$1.run(JMXConnectorSubjectForwarder.java:551)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9.run(JMXConnectorSubjectForwarder.java:549)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.setAttribute(JMXConnectorSubjectForwarder.java:544)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
    at javax.management.remote.rmi.RMIConnectionImpl.setAttribute(RMIConnectionImpl.java:683)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    javax.management.RuntimeMBeanException: Update failed, unknown property: LogicalDirectory
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doSetAttribute(OracleStandardEmitterMBean.java:761)
    at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalSetAttribute(ContextClassLoaderMBeanInterceptor.java:75)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalSetAttribute(MBeanRestartInterceptor.java:140)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalSetAttribute(AbstractMBeanSecurityInterceptor.java:142)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.setAttribute(OracleStandardEmitterMBean.java:709)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:762)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:699)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.setAttribute(JMXContextInterceptor.java:234)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.setAttribute(SecurityInterceptor.java:358)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.setAttribute(WLSMBeanServer.java:294)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9$1.run(JMXConnectorSubjectForwarder.java:551)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9.run(JMXConnectorSubjectForwarder.java:549)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.setAttribute(JMXConnectorSubjectForwarder.java:544)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
    at javax.management.remote.rmi.RMIConnectionImpl.setAttribute(RMIConnectionImpl.java:683)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.IllegalArgumentException: Update failed, unknown property: LogicalDirectory
    at oracle.fabric.management.composite.mbean.Binding.verifyValidProperty(Binding.java:668)
    at oracle.fabric.management.composite.mbean.Binding.setProperties(Binding.java:480)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doSetAttribute(OracleStandardEmitterMBean.java:753)
    at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalSetAttribute(ContextClassLoaderMBeanInterceptor.java:75)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalSetAttribute(MBeanRestartInterceptor.java:140)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalSetAttribute(AbstractMBeanSecurityInterceptor.java:142)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doSetAttribute(AbstractMBeanInterceptor.java:124)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.setAttribute(OracleStandardEmitterMBean.java:709)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:762)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:699)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.setAttribute(JMXContextInterceptor.java:234)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$14.run(WLSMBeanServerInterceptorBase.java:378)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.setAttribute(WLSMBeanServerInterceptorBase.java:376)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.setAttribute(SecurityInterceptor.java:358)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.setAttribute(WLSMBeanServer.java:294)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9$1.run(JMXConnectorSubjectForwarder.java:551)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$9.run(JMXConnectorSubjectForwarder.java:549)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.setAttribute(JMXConnectorSubjectForwarder.java:544)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
    at javax.management.remote.rmi.RMIConnectionImpl.setAttribute(RMIConnectionImpl.java:683)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Thanks Heidi. Some how, I think this might be related to the back and forth Jay Kasi and I have been having about the LogicalDirectory functionality of File Adapter. Coincidence that EM is complaining about that particular property in the trace?
    Please see:
    NPE validating a configuration plan in JDev
    -Todd

  • EM Console Service/Reference Property for Endpoint Ignored

    We are trying to use the BPEL Service\Reference Properties to set the Endpoint for one of our web services (and were under the impression that the reference properties can be modified at runtime in the EM Console). However, the default soap:address location is being picked up from the WSDL within the BPEL process when testing, and the service reference properties set at runtime completely ignored. Is there something else we need to set to test the BPEL process with an updated endpoint? We want to avoid changing the WSDL imported in the BPEL process and creating a new compile for each environment we want to deploy to.  We are on version 11.1.1.6.0.

    To use the endpoint property you need to define the property endpoint in the composite under the partnerlink. like this.
    reference name="HelloWorldSample" ui:wsdlLocation="HelloWorldSample.wsdl">
        <interface.wsdl interface="http://xmlns.oracle.com/TestApplication/First/BPELProcess1#wsdl.interface(BPELProcess1)"/>
        <binding.ws port="http://xmlns.oracle.com/TestApplication/Second/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)"
                    location="http://localhost:8001/soa-infra/services/default/First/bpelprocess1_client_ep?WSDL">
          <property name="endpointURI">http://localhost:8001/soa-infra/services/default/Second/bpelprocess1_client_ep</property>
        </binding.ws>
      </reference>
    You can also use the deployment config plan for each environment to change the endpoint urls of each wsdls.
    http://docs.oracle.com/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm

  • How to find path of a file in WebDynPro Application

    Hello,
    I have created a WebDynPro application. In this application i have created an XML file under
    src->packages->resources. The resources folder i created myself.
    I have also deployed the file on a remote server. This servername & portNumber can change too.
    Now i want to get the handle of my XML file (which is present in the same jar) so that i can user it and populate it.
    <b>The following code doesnt work:</b>
    <i>File file =new File("WebDynProProjectName/resources/filename.xml");</i>
    Regards,
    Aayush

    Hi
      By default it puts it under resources folder. If you want to create your own path then
    1. Create the XML file (eg. output.xml) to some location in the server (eg: c:\Test\files)
    2. Create a HTTP alias(eg. Test) in the Visual Adminsitrator pointing to the file location (eg: c:\Test\files).
    3. Set the linkToURL reference property to http://<<servername>>:50000/Test/<<XML file name>>
    For creating the HTTP alias refer to the blog "Creating an HTTP Alias in WAS"
    /people/renjith.andrews/blog/2005/03/31/creating-an-http-alias-in-was
    Hope this solves your problem.
    regards
    Ravi

  • Display interactive form as pdf document using LinkToURL UI

    Hi Experts
    I have an interactive form but I need to display as pdf document with a link. I tried to get the url:
    String templateUrl =
         WDURLGenerator.getWebResourceUrl(
         wdComponentAPI.getDeployableObjectPart(),
         "WDV_ARC_PDF_InteractiveFormMercantil.xdp");
    And modified the 'reference' property of 'LinkToURL' with this String.
    Please help me

    WebDynpro Java
    I need to display an interactive form like a pdf document, away the portal. Similar when you try to open a pdf document, appers the pop up window with the opcions: Open, Save ...
    Thanks

  • Call a "LinkToURL" element

    Hi community,
    I create a "LinkToUrl" element in View, this is to link an external application with reference property.
    I would like fire "action" of "LinkToURL" obj, from Event Handler.
    It's possible??
    Best Regards,
    Antonello

    Hi Antonello,
    Create a link to action UI element in the view .In the associated action write
    IWDWindow window = wdComponentAPI.getWindowManager().createExternalWindow("<url>", "<title>", false);
    //     for  opening the window.
         window.open();
    The third parameter is for determining whether the window is modal or not. so make it false
    You can also use a link to url for this
    specify the url in reference and make the target as _blank
    See the link for more details
    http://help.sap.com/saphelp_nw04/helpdata/en/5c/1b76bc3da0504e8b535cf3e154eaa7/frameset.htm
    Regards
    Rohit

  • How do I use a static reference to keep a VI in memory but then call it in parallel?

    Hello all,
    I have a MainVI and I want to call from it a SubVI in parallel so that I can have both windows open and responsive at the same time.  The SubVI may be closed and reopened any number of times, but only one in existance at a time.  I know how to do this using Open VI Reference, providing a relative path to my SubVI, checking its state to see if its already running, and if so bring the window to the front (using Front Panel: Open method with True/Standard inputs), and if not run it using the Invoke:Run method (and optionally opening its front panel programmatically).  This method was working fine.
    Now I have added functional global variables in my SubVI, and I want to keep them in memory inbetween opening the SubVI window.  I can do this by putting a copy of the functional global in my MainVI, even though I don't use it there for anything.  This works fine.
    By accident, I have come across a reference to a Static VI Reference, which sounded like a vast improvement to my methodology, for the following reasons:
    1) Keeps SubVI in memory all the time, eliminating the need to put the functional global in MainVI when it is not used there.
    2) Tells LabVIEW to include SubVI when I build my executable, rather than me having to specifically mark it as Always Include in the build specification.
    3) Eliminates the need to keep the path and SubVI name updated in a string constant in my code, in order to use the Open VI Reference.
    However, trying to implement this solution, I have run into the problem that once you put a strictly-typed static VI reference (strict typing is required to keep it in memory) onto the block diagram, that VI is reserved for execution.  That means I cannot run it using the Invoke:Run method.  I haven't tried just putting it on the diagram directly as a subVI because I need it to run in parallel to the MainVI.  I have searched through these forums extensively, and although there are several references to a static VI reference, none of them say explicitly how to actually run the darn thing!  :-P
    I very much appreciate any insight into my problem.  If I have to go back to the old way it will work fine, but I really like the seeming elegance of this solution.  I hope that it is technically feasible and I'm not misunderstanding something.
    Thank you for your help,
    -Joe
    Solved!
    Go to Solution.

    > If I understand you correctly, they can only really be used for re-entrant VIs. 
    No, a static VI reference can be used anywhere a regular VI reference (property nodes etc.) The reason for the hoop-jumping above is that we are really opening a reference to a CLONE (copy) of the VI identified by the static VI reference.
    > Okay, I tried it, and got the code shown below... Any idea why it isn't working?
    The VI you want to clone can't be on the diagram as a "normal" subVI. When you run your application you should be able to open that VI and see it just sitting there with a run arrow waiting to run. See attached example (LV2009SP1).
    "share clones" vs "preallocate" has to do with whether you want each clone to preserve state (such as in an uninitialized shift register). Generally you use share clones. Occasionally it is useful to have multiple copies on a diagram that each remember some data, like "timestamp of last execution" in a shift register.
    Other VIs in your spawned process don't have to be re-entrant unless they are functions that "wait forever". All the built-in G functions are re-entrant. It's pretty common to use a queue to feed data to a spawned process.
    Spawning a process is more difficult than just running two parallel loops. It's useful because once you've made 1 copy, you can make 50. If you just want to do two things (vs n things) at once, I would just use two loops.
    Attachments:
    SpawnProcess.zip ‏20 KB

  • Cross References Being Lost InDesign CS4

    I am setting up cross-references in a multiple
    document book using InDesign CS4 (Windows).
    When our editors open the files using InCopy CS4
    some of the cross-references are broken (little red flag icon appears).
    I've relinked the cross-references several times but everytime
    an InCopy user opens the file the cross-references are lost again.
    The sources and destinations are within the same document.
    I'm using Paragraph number as the cross-referencing method.
    Does it have something to do with the InDesign files being part of a Book?
    Any help would be great.
    Thanks, Bill

    wsterli wrote:
    I am setting up cross-references in a multiple
    document book using InDesign CS4 (Windows).
    When our editors open the files using InCopy CS4
    some of the cross-references are broken (little red flag icon appears).
    I've relinked the cross-references several times but everytime
    an InCopy user opens the file the cross-references are lost again.
    The sources and destinations are within the same document.
    I'm using Paragraph number as the cross-referencing method.
    Does it have something to do with the InDesign files being part of a Book?
    Any help would be great.
    Thanks, Bill
    It's possible that being a book component file that's separated from its other component files has some effect.
    I believe that x-refs look for a coded marker to keep up-to-date, not the paragraph number, so even if the numbers get out of whack because they continue from a previous file, this shouldn't cause the problem.
    I don't know how x-refs appear in IC. Is it possible to hover over the error indicator and see an explanation of the problem? If so, please post the message.
    Do the x-refs become resolved when you return the document to the book in ID?
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices

  • SQL Query to list the "Optional reference" field of all packages in cm 2012

    Guys, could you please point me to the correct view to extract the "Optional reference" property of all application? I've got a powershell script to get that from WMI, but i really am expecting a way to extract it from ConfigMgr DB if that's
    available in CM Db.
    Thanks,
     Delphin.
    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

    Thank you torsten for helping me out here.
    I've managed to come up with a query to list the Display name, package verison and optional reference property.
    ;WITH XMLNAMESPACES ( DEFAULT 'http://schemas.microsoft.com/SystemCenterConfigurationManager/2009/AppMgmtDigest')
    select DisplayName, SDMPackageDigest.value('(/AppMgmtDigest/Application/CustomId/@ResourceId)[1]', 'nvarchar(10)') [Optional Reference]
    ,sdmpackageversion
    from fn_ListApplicationCIs(1033)
    order by DisplayName
    But the problem here is, I'm looking for the value AB00001 from that XML but it actually giving me Res_631986121. Can someone help me to get the value AB00001 from that xml file? 
    <CustomId ResourceId="Res_631986121">AB00001</CustomId>
    Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin

  • Can I build a waveform reference

    I am using Labview 6 and would like to build a wave form reference property node. I want to do this so that I can use a for loop to create a series of waveform names and feed them to one property node , is this possible??

    I don't think you can do that in one easy shot. You might need to put all of the waveforms in a cluster and then pull out each waveform, rename it, and then insert it back into the cluster.

  • Dynamically load a VI by library reference

    We are very excited by the introduction of project libraries in LV8 and what it means for project management and building multiple custom distributions using libraries of dynamically called VIs from within a single project.  We now have our VIs arranged by VI "type" in the directory structure and by logical "function" with the project libraries that make up the project.  It sure wold be nice if we could dynamically load VIs from the library reference rather than trying to keep up with the actual paths.  I can get a reference to the library using and invoke node and "open.library" with a path wired in.  Is there any way to use this library reference to do an "open vi reference" to a VI within that library?

    Hello Lee,
    This invoke node returns a reference to the libray, with this you can browse throught the library just like a tree control. It is usefull to open the .lvlib file with a text editor to see what 'Type string' options you have. If you get to the right VI use the 'VI Reference' property from the 'Library Item'-class, this will get you a reference to the VI which you can open, edit, save or whatever VI-server offers you.
    Good luck
    Ton
    PS I'm using in this in a tool to duplicate the .lvproj structue into the hard-drive, I'm not fully done but getting there!
    PS This screenshot was made with Starware
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!
    Attachments:
    Example_BD.png ‏2 KB

  • Closing ADODB sub reference outs in VIs? (LV 8.5.1)

    I had a question about closing references to items I have not explicitly opened.
    e.g.
    I create an ADODB connection object.
    From that, I create an ADODB command object.
    One of the Command properties is the Parameters reference. I do a parameters.Refresh and using count, I loop through a For loop getting Item references. For each Item reference, I get a parameter object.
    One of the properties in the parameter object is a Properties reference.  I do a refresh on that and then go into another For loop. For each Item reference, I get a property node.
    OK, now that I've gone through getting/setting information, I need to start working my way out. The last property node had an item reference out from the properties node. Should I close that? The properties node itself had as a reference out, should that be closed? The Parameter node has a reference out, should that be closed? Finally, the Parameters node has a reference out, should I close that?
    The command and connection nodes I explicitly opened, so I know I need to close them. But these other references, should I be closing them, or do I only need to close the references I explicitly created?
    Thanks, Bob

    "intp56" <[email protected]> wrote in message
    news:[email protected]..
    > I download LabSQL, it looks pretty close to what I want.
    > &nbsp;
    I'd suggest to use it, and to send them your additional code in return if
    you're alowed to do that... Or suggest what you are missing to the project,
    so they can add it in later versions.
    > I'm looking for a VI that queries a stored procedure to determine what the
    parameters are, then creates a LabVIEW cluster with the correct datatypes.
    The idea is to call that first to create the Parameters object, then use it
    later, particularly for DML operations. (Say insert rows from a LV table.)
    I've tried using ADO recordsets to insert large datasets, and found it's
    performance to be lacking or unacceptable. I can insert several 1000 records
    per second with successive calls to a stored procedure where I specify ahead
    of time no result set.
    Not sure how ADO does this. I vaguely recall something about it. I think the
    values are send item by item, and I think there was a faster way to send the
    data by using a variant that directly accepts an array... It's been a while
    since I've messed around with that, and I might not have succeeded to get it
    working. Googling for "ADO large data sets" or something might give some
    clues.
    > If I really have lots of rows to insert, then I've found it better to
    prepare a file, move it to a place where the database can see it, and BULK
    INSERT it asynchronously and report the results back later.
    Can't imagine that this is the best way to do it, but it's a good
    workaround.
    > BTW, I liked the tip that any reference WIRE needs to be closed, that
    gives me a nice rule to know what I need to closed.
    But even if there is no wire comming out of a reference property, you still
    need to close it. So: every "green" read property should be closed.
    Regards,
    Wiebe.

  • How to change value of array element using property node

    hello all : )
    im using an array of combo-box. the size of array is not fixed.
    i want to use the strings[ ] property of combo-box to enter selection texts but since i have placed it inside the array im unable to use this property.
    i used 'arrayelem' reference property and connected property node to it but didnt got strings [ ] in the selection.
    so is there any way i can use the strings [ ] property
    Solved!
    Go to Solution.

    the picture what I posted is a snippet. It is a png file which also contains a vi:
    http://www.ni.com/tutorial/9330/en/
    I have found this post. I am just reading it:
    http://forums.ni.com/t5/LabVIEW/combobox-in-array-why-does-it-work-this-way/m-p/2146916/highlight/tr...
    It might help...
    hmm, it is more complicated as I thought )
    edit: just to be CLEAR: so you want to create a new selection LIST for each of the array elements (comboboxes)) OR you just want to set all the comboboxes to a particular value which is ALREADY in the combobox list??

Maybe you are looking for