Best Practice for "flag" columns

Hello Experts!
This is more of a design/architecture/performance? question. Suggestions welcome, of course!
Oracle Server version 11.2.0.3
Scenario:
I plan to use one of my columns in the table as a "flag" field. Meaning, this field will have some type of static value. Our document management system leverages Oracle as the database and provides a front-end user interface for the user. When the user searches for their documents, the records will be displayed accordingly. If the user wants to "delete" the document, they would change the flag field from "No" to "Yes". The custom search that we would have already built for them would have a hidden where clause of "where column_flag = 'No'" to show the records that they searched and of course if they change the flag to "Yes" (to be deleted), it will no longer appear in their search results. The field would be a string datatype.
My Second Thought:
Same scenario above, except for 1 change. Instead of the "No" and "Yes" value, I would replace the value to a blank/null value and "Delete". Essentially, the drop-down value would change from "No" and "Yes" values to a blank value and "Delete". Visually, this would make more sense to our users when they see the data and for when they decide to choose to "delete" a document. At this point, the where clause would of course change to "where column_flag is null".
My Question:
From a performance perspective, which is a better practice?
Is it faster to query the database with "where column_flag = 'No'" / "where column_flag = 'Yes'" OR "where column_flag is null" / "where column_flag = 'Delete'"?
Should I even create an index on the column? (I would assume no because it would serve no benefit because of the static values).
Keep in mind that I will have millions and millions of records/rows in the table. I am striving for the best possible answer in terms of long-term performance. In the past, I have had users complain about "slow searches" and that is what I would like to help prevent from happening.
Thanks in advance for all your help and suggestions!

rp0428 wrote:
When the user searches for their documents, the records will be displayed accordingly. If the user wants to "delete" the document, they would change the flag field from "No" to "Yes". The custom search that we would have already built for them would have a hidden where clause of "where column_flag = 'No'" to show the records that they searched and of course if they change the flag to "Yes" (to be deleted), it will no longer appear in their search results.
Why? If you user wants to delete the document just delete it. Then you don't need ANY of the mucking around.
What is it you aren't telling us? Why would you just mark it instead of actually delete it?
The reason is because of senior upper management policy, where they do not want to actually delete/remove the record from the system. They only want to "delete"/hide the record from the search result from the user if they choose to "delete" a document. Part of this is to help prevent a restore from happening. Lets say a user accidentally deletes (an actual real delete) of a document and the next day/week/month/year she says, "oops, I made a mistake can you undo it?" The answer is yes, but then we now lose more documents/data just to restore that 1 document because of all the other documents that were added to the system the previous day. Make sense? However, in this scenario, if they just mark it for "deletion" and they think that they are actually deleting it, but what it's really doing is hiding it from their search results, then if she comes and says, "oops, I made a mistake can you undo it?" We can simply change the flag/property from "Yes" to "No" (or from one to the other basically, and assuming she provides us with all the necessary information for the document for us to find it) and then we don't have to actually perform a system "restore" any thing.
rp0428 wrote:
Is it faster to query the database with "where column_flag = 'No'" / "where column_flag = 'Yes'" OR "where column_flag is null" / "where column_flag = 'Delete'"?
Not enough info to know. Query performance will depend on the query, all of the data needed for the query, indexes available and other things.
The query will always have this hidden where clause of "where column_flag = 'No'" in the front-end UI for the user. The UI for the user basically has pertinent information for them to search off of for a particular set of documents with the additional where clause to search for documents that are not marked for deletion. For instance, HR would have searchable fields, like FirstName, LastName, EmployeeID, SocialSecurityNumber, etc.. the user has the ability to search for any of these fields and when they populate any of these fields and clicks search, it goes out and retrieves all of the documents that are found based on the criteria entered. The additional where clause of "where column_flag = 'No'" will always be added somewhere in the where clause of the SQL query because we only want to display documents that are not marked for deletion. We have no reason nor should they have any reason to see documents that they "deleted" because to them they will think that they are actually deleting/removing the document from the system when they change the flag/property.
rp0428 wrote:
Should I even create an index on the column? (I would assume no because it would serve no benefit because of the static values).
Not enough info to know. If there are 5 million YES values and 5 million NO values what purpose would an index serve? As SB said if NULL means YES but nulls aren't indexed then what purpose would an index server?
The most likely case where an index on that one column would be used is if the mosts commonly queried value is rare. More likely the actual table row will need to be obtained from the table and the filter of Y/N can be applied then.
For a simple flag just use VARCHAR2(1). There is no need to store YES or NO; that just increase the amount of storage needed for no benefit.
The majority of the documents would not be marked for deletion or would not have "No". Lets say if I had 10 million records/rows in the database, I would probably say that less than 1%? would probably be marked for deletion by the users, which is 1 million documents or less. Realistically, I would probably even go further to say that out of 10 million, I could only imagine that maybe ~50,000 would only be marked for deletion? The number is not very high and would be uncommon for the users to consistently delete documents.

Similar Messages

What is the best practice for inserting (unique) rows into a table containing key columns constraint where source may contain duplicate (already existing) rows?

My final data table contains a two key columns unique key constraint. I insert data into this table from a daily capture table (which also contains the two columns that make up the key in the final data table but are not constrained
(not unique) in the daily capture table). I don't want to insert rows from daily capture which already exists in final data table (based on the two key columns). Currently, what I do is to select * into a #temp table from the join
of daily capture and final data tables on these two key columns. Then I delete the rows in the daily capture table which match the #temp table. Then I insert the remaining rows from daily capture into the final data table.
Would it be possible to simplify this process by using an Instead Of trigger in the final table and just insert directly from the daily capture table? How would this look?
What is the best practice for inserting unique (new) rows and ignoring duplicate rows (rows that already exist in both the daily capture and final data tables) in my particular operation?
Rich P

Please follow basic Netiquette and post the DDL we need to answer this. Follow industry and ANSI/ISO standards in your data. You should follow ISO-11179 rules for naming data elements. You should follow ISO-8601 rules for displaying temporal data. We need
to know the data types, keys and constraints on the table. Avoid dialect in favor of ANSI/ISO Standard SQL. And you need to read and download the PDF for:
https://www.simple-talk.com/books/sql-books/119-sql-code-smells/
>> My final data table contains a two key columns unique key constraint. [unh? one two-column key or two one column keys? Sure wish you posted DDL] I insert data into this table from a daily capture table (which also contains the two columns that make
up the key in the final data table but are not constrained (not unique) in the daily capture table). <<
Then the "capture table" is not a table at all! Remember the fist day of your RDBMS class? A table has to have a key. You need to fix this error. What ETL tool do you use?
>> I don't want to insert rows from daily capture which already exists in final data table (based on the two key columns). <<
MERGE statement; Google it. And do not use temp tables.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

Best practice for phone number column data type

Hi,
I hope I have posted this in the right forum, if not just notify me and i will remove it to the correct area.
What would be considered best practice for storing a phone number.
Number of Varchar2.
Ben

Well I was thinking that Number would have the following disadvantages,
1. Users entering phone numbers into a form may be tempted to pre format with spaces, thereby throwing up an error.
2. Mobile phone numbers may have leading zeros
3. Calculations are not carried out on phone numbers.
I was leaning towards a varchar2 type.
Ben

Best Practice for Using Static Data in PDPs or Project Plan

Hi There,
I want to make custom reports using PDPs & Project Plan data.
What is the Best Practice for using "Static/Random Data" (which is not available in MS Project 2013 columns) in PDPs & MS Project 2013?
Should I add that data in Custom Field (in MS Project 2013) or make PDPs?
Thanks,
EPM Consultant
Noman Sohail

Hi Dale,
I have a Project Level custom field "Supervisor Name" that is used for Project Information.
For the purpose of viewing that "Project Level custom field Data" in
Project views , I have made Task Level custom field
"SupName" and used Formula:
[SupName] = [Supervisor Name]
That shows Supervisor Name in Schedule.aspx
============
Question: I want that Project Level custom field "Supervisor Name" in
My Work views (Tasks.aspx).
The field is enabled in Task.aspx BUT Data is not present / blank column.
How can I get the data in "My Work views" ?
Noman Sohail

What is best practice for conditional rendering?

i have a set of radio buttons that conditionally render another set, which in turn conditionally render a 3rd set.
i am doing this by using a valueChangeListener on an h:selectOneRadio
when i click yes on the 1st set it renders the 2nd set.
when i click yes on the 2nd set it renders the 3rd set.
when i click no on the 1st set now it correctly removes the 2nd & 3rd sets, the method also nulls the values.
when i click yes on the 1st set, it renders the 2nd set with the old values even though they were nulled. and i can see in the debugger they are still null.
so there seems to be an issue updating the model, but i dont know what that issue is. im sure it just has something to do with the way i am trying this conditional render. please see below for my first field and my valueChangeListener method.
any help with what is a best practice for this scenario would be greatly appreciated.
<h:panelGrid id="grid20a" columns="1">
                         <h:outputText value="Does this consult pertain to a specific "/>
                         <h:outputText value="planned or ongoing research project?: *"/>
                    </h:panelGrid>
                    <h:selectOneRadio id="specificResearch1" value="#{ethicsConsultBacking.bean.specificResearch}"
                         layout="lineDirection" required="true"
                         valueChangeListener="#{ethicsConsultBacking.processValueChangeSpecificResearch}">
                              <f:selectItems value="#{ethicsConsultBacking.yesNoMap}" />
                              <a4j:support event="onclick" reRender="form"/>
                    </h:selectOneRadio>
                    <h:message for="specificResearch1" styleClass="redText" />
public void processValueChangeSpecificResearch(ValueChangeEvent e) throws AbortProcessingException
          String newValue = e.getNewValue().toString();
          //reinitialize
          this.setRenderHumanSubjectResearch(false);
          this.setRenderIrbSection(false);
          this.setRenderIrbProtocolNumber(false);
          this.getBean().setHumanSubjectResearch(null);
          this.getBean().setPrimaryIrb(null);
          this.getBean().setIrbStatus(null);
          this.getBean().setIrbProtocolNumber(null);
          //check condition
          if (newValue.equalsIgnoreCase(this.YES))
               this.setRenderHumanSubjectResearch(true);
           * Clearing validation messages.
           * This will get around the issue with having a field
           * on the form that is both required & immediate.
          Iterator it = this.getFacesContext().getMessages();
          while (it.hasNext())
               it.next();
               it.remove();
          this.getFacesContext().renderResponse();
     }i also tried doing this another way by just using an action method attached to the a4j:support tag, but that introduced a different set of issue. so ill leave that out for now unless that is the direction someone would like to direct my issue in.
Thanks in advance

Similar issue is covered and explained here: [http://balusc.blogspot.com/2007/10/populate-child-menus.html]. Not sure if it solves your problem as you're using ajax4jsf whereas I don't, but it might give new insights. To the point you might need to bind the component(s) and use setValue(null) or setSubmittedValue(null).

Best practice for importing non-"Premiere-ready" video files

Hello!
I work with internal clients that provide me with a variety of differnet video types (could be almost ANYTHYING, WMV, MP4, FLV). I of course ask for AVIs when possible, but unfortunately, I have no control over the type of file I'm given.
And, naturally, Premiere (just upgraded to CS5) has a hard time dealing with these files. Unpredictable, ranging from working fine to not working at all, and everything in between. Naturally, it's become a huge issue for turnaround time.
Is there a best practice for preparing files for editing in Premiere?
I've tried almost everything I can think of: converting the file(s) to .AVIs using a variety of programs/methods. Most recently, I tried creating a Watch Folder in Adobe Media Encoder and setting it for AVI with the proper aspect ratio. It makes sense to me that that should work:using an Adobe product to render the file into something Premiere can work with.
However, when I imported the resulting AVI into Premiere, it gave me the Red Line of Un-renderness (that is the technical term, right?), and had the same sync issue I experienced when I brought it in as a WMV.
Given our environment, I'm completely fine with adding render time to the front-end of projects, but it has to work. I want files that Premiere likes.
THANK YOU in advance for any advice you can give!
-- Dave

I use an older conversion program (my PrPro has a much older internal AME, unlike yours), DigitalMedia Converter 2.7. It is shareware, and has been replaced by Deskshare with newer versions, but my old one works fine. I have not tried the newer versions yet. One thing that I like about this converter is that it ONLY uses System CODEC's, and does not install its own, like a few others. This DOES mean that if I get footage with an oddball CODEC, I need to go get it, and install it on the System.
I can batch process AV files of most types/CODEC's, and convert to DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio and at 29.97 FPS (I am in NTSC land). So far, 99% of the resultant converted files have been perfect, whether from DivX, WMV, MPEG-2, or almost any other format/CODEC. If there is any OOS, my experience has been that it will be static, so I just have to adjust the sync offset by a few frames, and that takes care of things.
In a few instances, the PAR flag has been missed (Standard 4:3 vs Widescreen 16:9), but Interpret Footage has solved those few issues.
Only oddity that I have observed (mostly with DivX, or WMV's) is that occasionally, PrPro cannot get the file's Duration correct. I found that if I Import those problem files into PrElements, and then just do an Export, to the same exact specs., that resulting file (seems to be 100% identical, but something has to be different - maybe in the header info?) Imports perfectly into PrPro. This happens rarely, and I have the workaround, though it is one more step for those. I have yet to figure out why one very similar file will convert with the Duration info perfect, and then a companion file will not. Nor have I figured out exactly what is different, after running through PrE. Every theory that I have developed has been shot down by my experiences. A mystery still.
AME works well for most, as a converter, though there are just CODEC's, that Adobe programs do not like, such as DivX and Xvid. I doubt that any Adobe program will handle those suckers easily, if at all.
Good luck,
Hunt

Best practices for customizing the standard OBIA metedata repository (RPD)

Hello
Is there a Best practices document published by oracle or a partner that talks about best practices for customizing OBIA out-of-box RPD. I am specifically looking for guidance around:
1. adding new objects to physical layer or modifying an exisitng table definition to add more columns
2. Building new Logical columns in BMM layer
3. Modifying the exisitng Subject areas.
Thanks

There is a very good presentation by Rittman mead on extending and customizing BI Applications. Refer to this link (http://www.rittmanmead.com/files/OOW2008%20-%20Extending%20and%20Customizing%20the%20BI%20Apps%20Data%20Warehouse.pdf ).
Thanks,
-Amith.

Best practices for XMLType to RDMS migration

We are storing XBRL files (basically XML) into oracle 11.2 as XMLType. Each XML files containing more than 500 tags. For reporting purpose we are extracting around 200 values from XML files to normal tables (NORMAL_TABLE).Reading from XML file directly is taking more execution time so we are doing migration as job from XMLType to NORMAL_TABLE. Basically each row in NORMAL_TABLE represent each XML files, that mean now we have around 200 columns in NORMAL_TABLE.
Because of new requirement and CR , now we need more values to be migrate from XML to NORMAL_TABLE. Which would be the best practices for this case? Is it ok to add more columns into NORMAL_TABLE ?

The link is not working (Error Page 404), maybe this one can help:
[http://www.oracle.com/technetwork/database-features/xmldb/xmlqueryoptimize11gr2-168036.pdf]
Actually, It's not about RDBMS migration, but I think it can help anyway.

Seeking advice on Best Practices for XML Storage Options - XMLTYPE

Sparc64
11.2.0.2
During OOW12 I tried to attend every xml session I could. There was one where a Mr. Drake was explaining something about not using clob
as an attribute to storing the xml and that "it will break your application."
We're moving forward with storing the industry standard invoice in an xmltype column, but Im not concerned that our table definition is not what was advised:
--i've dummied this down to protect company assets
CREATE TABLE "INVOICE_DOC"
   (     "INVOICE_ID" NUMBER NOT NULL ENABLE,
     "DOC" "SYS"."XMLTYPE" NOT NULL ENABLE,
     "VERSION" VARCHAR2(256) NOT NULL ENABLE,
     "STATUS" VARCHAR2(256),
     "STATE" VARCHAR2(256),
     "USER_ID" VARCHAR2(256),
     "APP_ID" VARCHAR2(256),
     "INSERT_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
     "UPDATE_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
      CONSTRAINT "FK_####_DOC_INV_ID" FOREIGN KEY ("INVOICE_ID")
             REFERENCES "INVOICE_LO" ("INVOICE_ID") ENABLE
   ) SEGMENT CREATION IMMEDIATE
INITRANS 20
TABLESPACE "####_####_DATA"
       XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" ENABLE STORAGE IN ROW CHUNK 16384 RETENTION
NOCACHE LOGGING
STORAGE(INITIAL 81920 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
XMLSCHEMA "http://mycompanynamehere.com/xdb/Invoice###.xsd" ELEMENT "Invoice" ID #####"
{code}
What is a best practice for this type of table? Yes, we intend on registering the schema against an xsd.
Any help/advice would be appreciated.
-abe

Hi,
I suggest you read this paper : Oracle XML DB : Choosing the Best XMLType Storage Option for Your Use Case
It is available on the XML DB home page along with other documents you may be interested in.
To sum up, the storage method you need depends on the requirement, i.e. how XML data is accessed.
There was one where a Mr. Drake was explaining something about not using clob as an attribute to storing the xml and that "it will break your application."I think the message Mark Drake wanted to convey is that CLOB storage is now deprecated and shouldn't be used anymore (though still supported for backward compatibility).
The default XMLType storage starting with version 11.2.0.2 is now Binary XML, a posted-parsed binary format that optimizes both storage size and data access (via XQuery), so you should at least use it instead of the BASICFILE CLOB.
Schema-based Binary XML is also available, it adds another layer of "awareness" for Oracle to manage instance documents.
To use this feature, the XML schema must be registered with "options => dbms_xmlschema.REGISTER_BINARYXML".
The other common approach for schema-based XML is Object-Relational storage.
BTW... you may want to post here next time, in the dedicated forum : {forum:id=34}
Mark Drake is one of the regular user, along with Marco Gralike you've probably seen too at OOW.
Edited by: odie_63 on 18 oct. 2012 21:55

Best practices for Refreshing Unv Structure for SAP based universes

This may sound basic and I apologize for asking this, but the refresh structure in SAP based universes is somewhat different from noraml universes.
Here is what i'd like to do:
- Hide all the L00 objects.
- Rename all the L01 objects and move them to a new Class.
- Change some of the detail (attribute) objects to dimension objects.
- Hide the format and Unit for key figures.
- Hide all of the classes/subclasses that get automatically generated when a SAP based universe is created.
I have noticed that when I do the above and refresh the universe, it assumes that all these objects have gone missing from the original classes and adds them back to the universe.
I also want to make sure that if the select of an object gets updated and the object is re-named, then it should automatically pick up the change.
Lastly, I have some reports which were built prior to this renaming. I want to make sure that the reports do not break.
Thanks,
Kashif

Hi,
This thread is really old.
Yes it was a common problem back in the earlier XI 3.x days . a lot of bugs in this area were eliminated by the time of XI 3.1 SP03 FP3.x - you don't quote your version.
Actually, you need to be aware that a refresh structure is often not needed, and can corrupt the olap universe . Pls check out Note 1278216 - What are the best practices for OLAP Universe Change Management when using SAP Integration Kit?
in essence :
Only use 'Refresh Structure' functionality If:
- A new Object (Dimension/Characteristic) has been added to the BEx query (Rows/Columns/Free Characteristics)
- A new Variable Restriction has been added to the Bex query Filters
Do not use 'Refresh Structure' functionality after:
- Having modified a STRUCTURE in BEx. i.e. 'Detail view of Formula' or 'Details of Selection', or changing the General Description of structure members.
- Doing manual actions on objects/classes in the OLAP Universe like: Move ; Cut/Paste ; Drag/Drop ; Hide ; Delete.
(because these workflow can lead to corruption)
regards,
H

Limitation/Best Practices for O BIP.....

Hi All,
can some one discuss Limitation/Best Practices for O BIP.....like number of fields or columns to be used in reporting amount of data used Etc...
Cheers....

Hi,
So You say u can keep as many as columns in BIP report?
But unfortunately we can keep only 63 cloumns in report, a question is not an answer for a question. iam sure because i faced this issue.
the forum is meant to share unknow things, if you are interested you can join. Else people who are interested will join
If you are not interested please don't make thing go other way.....
Thanks
Cheers...........

Best practices for setting up users on a small office network?

Hello,
I am setting up a small office and am wondering what the best practices/steps are to setup/manage the admin, user logins and sharing privileges for the below setup:
Users: 5 users on new iMacs (x3) and upgraded G4s (x2)
Video Editing Suite: Want to connect a new iMac and a Mac Pro, on an open login (multiple users)
All machines are to be able to connect to the network, peripherals and external hard drive. Also, I would like to setup drop boxes as well to easily share files between the computers (I was thinking of using the external harddrive for this).
Thank you,

Hi,
Thanks for your posting.
When you install AD DS in the hub or staging site, disconnect the installed domain controller, and then ship the computer to the remote site, you are disconnecting a viable domain controller from the replication topology.
For more and detail information, please refer to:
Best Practices for Adding Domain Controllers in Remote Sites
http://technet.microsoft.com/en-us/library/cc794962(v=ws.10).aspx
Regards.
Vivian Wang

Best-practice for Catalog Views ? :|

Hello community,
A best practice question:
The situtation: I have several product categories (110), several items in those categories (4000) and 300 end-users. I would like to know which is the best practice for segment the catalog. I mean, some users should only see categories 10,20 & 30. Other users only category 80, etc. The problem is how can I implement this ?
My first idea is:
1. Create 110 Procurement Catalogs (1 for every prod.category). Each catalog should contain only its product category.
2. Assign in my Org Model, in a user-level all the "catalogs" that the user should access.
Do you have any idea in order to improve this ?
Saludos desde Mexico,
Diego

Hi,
Your way of doing will work, but you'll get maintenance issues (to many catalogs, and catalog link to maintain for each user).
The other way is to built your views in CCM, and assign these views to the users, either on the roles (PFCG) or on the user (SU01). The problem is that with CCM 1.0 this is limitated, cause you'll have to assign one by one the items to each view (no dynamic or mass processes), it has been enhanced in CCM 2.0.
My advice:
-Challenge your customer about views, and try to limit the number of views, with for example strategic and non strategic
-With CCM 1.0 stick to the procurement catalogs, or implement BADIs to assign items to the views (I experienced it, it works, but is quite difficult), but with a limitated number of views
Good luck.
Vadim

Best Practice for Securing Web Services in the BPEL Workflow

What is the best practice for securing web services which are part of a larger service (a business process) and are defined through BPEL?
They are all deployed on the same oracle application server.
Defining agent for each?
Gateway for all?
BPEL security extension?
The top level service that is defined as business process is secure itself through OWSM and username and passwords, but what is the best practice for security establishment for each low level services?
Regards
Farbod

It doesnt matter whether the service is invoked as part of your larger process or not, if it is performing any business critical operation then it should be secured.
The idea of SOA / designing services is to have the services available so that it can be orchestrated as part of any other business process.
Today you may have secured your parent services and tomorrow you could come up with a new service which may use one of the existing lower level services.
If all the services are in one Application server you can make the configuration/development environment lot easier by securing them using the Gateway.
Typical probelm with any gateway architecture is that the service is available without any security enforcement when accessed directly.
You can enforce rules at your network layer to allow access to the App server only from Gateway.
When you have the liberty to use OWSM or any other WS-Security products, i would stay away from any extensions. Two things to consider
The next BPEL developer in your project may not be aware of Security extensions
Centralizing Security enforcement will make your development and security operations as loosely coupled and addresses scalability.
Thanks
Ram

Best practice for multi-language content in common areas

I've got a site with some text in header/footer/nav that needs to be translated between an English and Spanish site, which use the same design. My intention was to set up all the text as content to facilitate. However, if I use a standard dialog with the component's path set to a child of the current page node, I would need to re-enter the text on every page. If I use a design dialog, or a standard dialog with the component's path set absolutely, the Engilsh and Spanish sites will share the same text. If I use a standard dialog with the component's path set relatively (eg path="../../jcr:content/myPath"), the pages using the component would all need to be at the same level of the hierarchy.
It appears that the Geometrixx demo doesn't address this situation, and leaves copy in English. Is there a best practice for this scenario?

I'm finding that something to the effect of <cq:include path="<%= strCommonContentPath + "codeEntry" %>" resourceType ...
works fine for most components, but not for parsys, or a component containing a parsys. When I attempt that, I get a JS error that says "design.path is null or not an object". Is there a way around this?

Best Practice for "flag" columns

Similar Messages

Maybe you are looking for